Skip to content

Sharing a page ​

The Share dialog says who may open this page, and at what level. A grant here applies to everything underneath it in the page tree.

The four levels are none, read, comment and write. The full rule — how roles, grants, groups and inheritance resolve — is in roles and permissions; this page is about the dialog.

Who you can share with ​

Four kinds of subject, and the dialog is explicit about which one you are naming:

SubjectMeans
A personOne account, by email.
A groupA named set of this workspace's people. See groups.
Everyone in the workspaceEverybody holding a membership here, guests included.
A whole workspaceEverybody who belongs to another workspace, by its address.

The subject must be stated. There is no default, because a default that is the broadest of its options is a default nobody should have to know about.

What "everyone" means

Everyone in the workspace means everybody holding a membership here — not everybody with an account on the deployment. That distinction was once a real breach: a page a workspace opened to its own team was readable by any signed-in stranger, along with its place in the tree, its search hits and a live editing socket. The rule now consults membership, and the check is a required argument so no future call site can silently skip it.

Sharing outside the workspace ​

A page shared with somebody in another workspace is modelled as visiting, not importing. They open it at your workspace's address; they hold no membership there, so they get exactly what you granted and nothing else.

It appears for them under Shared with you in the sidebar, deliberately kept out of their page tree — those pages are not their workspace's, and putting them in the tree would say they were.

Granting to a whole workspace saves you maintaining a list of individuals that goes stale the moment the other organisation hires somebody. The trade is stated in the dialog rather than left to be discovered: one grant reaches everybody there, including whoever joins later, and stops reaching anybody who leaves.

Every outward grant is written to the audit log — the granting workspace's log says what it opened, and the receiving workspace's says what was opened to it, because an admin whose whole workspace was just handed somebody else's document has no other way to learn that. Internal sharing is not logged: it happens constantly, and recording it would bury the entries the log exists to make visible.

What a reader actually gets ​

A read-only page opens without a caret. That is not the whole enforcement, though — the socket refuses what a reader sends anyway. The caret is there so you find out before you type, not because it is the security boundary.

Attachments follow the page: somebody who may read a page may fetch the files on it, and somebody who may not, cannot. See attachments.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.