Workspaces and sharing

A workspace owns your shared content. Guides, guide files and context bundles each belong to one, and who can reach them is decided by who belongs to that workspace.

Your personal workspace

You get one the first time you save anything. It is called Personal, you are its only member, and you never had to make it.

You cannot invite anyone into it. That refusal is deliberate: your personal workspace holds everything you have ever saved, so an invitation into it is the “I invited a contractor and they saw all of it” mistake. To share something, make a second workspace and move the bundle there.

Inviting someone

Only an owner of a workspace can invite or remove people. Whoever creates a workspace is its owner. Invite by email address, from Settings → Workspaces.

The invited address gets one mail, which names you and the workspace so the recipient can judge it. They do not need an account first. If they sign up with that address the invitation is waiting for them.

Inviting the same address twice is the same invitation rather than a second one, and Mossbear sends the mail once per invitation that was actually delivered.

Nothing is shared until they accept. Accepting adds them as a member, never an owner: ownership transfers, it is not granted by an invite. Declining tells you only that the invitation is closed.

What a member can then see

Membership is the whole of the answer. Every endpoint that reads or writes a shareable row asks the same question: is there a membership row joining this row’s workspace to this user. There is no second path in, and your user id is not a fallback. A row that names no workspace matches nothing and is refused rather than treated as its author’s, so someone who leaves a workspace loses access to the rows they wrote while in it.

That question is asked inside the statement it guards, so revoking membership takes effect on the next read rather than at the end of some cached window.

Guides are shared. Verdicts are not.

This is the part people expect to work the other way.

When your dashboard grades one of your sessions, it grades against every active guide you can reach: your own, plus the ones a teammate shared into a workspace you belong to. A standard your team agreed on applies to your sessions without you copying it into your repo.

Each shared guide arrives with its author’s own grading criteria, so a teammate’s guide is judged by the rubric its author wrote rather than by none.

Your verdicts go nowhere. Sessions, actions and guide verdicts are scoped to the user who produced them, permanently. A teammate in your workspace sees the guides you share and cannot see how any of your sessions scored against them. Sharing a standard is not sharing your performance.