Original source · exact version bafyreiakigkvlrdul5l56lka3u5hfzf6n3olxuv7ism5eybtxbohnedyce · Read-derived block

Classification: story; source kind: story; decision: approve; confidence: high; review status: needs-review.

Rationale: Document-scoped sharing is an actual story with detailed criteria; contextual-menu cleanup is ancillary design feedback, not a replacement acceptance criterion. Partial overlap: 0047 repeats invitation channels and role management at space scope; 0045 establishes visibility defaults; 0041 is the nonmember requesting access, not an admin/writer granting it. These are distinct actors/scopes, not confirmed duplicates.

Review qualification: Uncertain identity/behavior/duplication remains a separate candidate; do not merge without review.

Canonical target (to be published after manifest): Proposed canonical target

Similar source candidates — kept separate

spacea-ccess

level-of-privacy

as-a-user-i-have-a-link-from-a-private-space

Evidence snapshot: original readable text and block backlinks

Heading As an admin, or writer I want to give access to my document(s) so that I can control who sees and contributes to them. source block

Heading Acceptance criteria source block

Heading Sharing access source block

Paragraph Admins and writers can share a document or group of documents through contextual actions in the document or its preview - (⋯). source block

Paragraph Private documents only support invitations by email — On a first stage, people can be found by searching for users who already have a Seed account. source block

Paragraph Public documents support invitations by email and link. — On a first stage, searching and link. source block

Heading Space and document visibility source block

Paragraph In Public spaces, admin can make individual documents private. source block

Paragraph In Private spaces, documents cannot be made public. source block

Paragraph Inviting someone to a document in a Private space limits access to that document and its subdocuments. source block

Paragraph Inviting someone to a document in a Public space grants access to the whole space. source block

Paragraph In a Public space, document sharing just preview people who has writer role. source block

Heading Inheritance and permission management: source block

Paragraph Document-sharing permissions cascade to subdocuments. source block

Paragraph People invited to a parent document cannot be removed from its children. source block

Paragraph Additional people can be invited to child documents. source block

Paragraph Admins can change roles and remove access. source block

Paragraph Writers can change roles and remove access, except for admins. source block

Heading How access is given: source block

Paragraph Admin or writer can give access to a document or group of documents from contextual actions in the document itself or in the document preview. source block

Paragraph In a Public space, admins can make individual documents private. source block

Paragraph In a Private space, documents cannot be made public. source block

Heading Design source block

Paragraph Sharing access to a document on a public space source block

Original link/embed source block

Paragraph Sharing access to a document on a private space source block

Original link/embed source block

Paragraph In the first stage by looking for a member name who already has an account on Seed. source block

Original link/embed source block

Heading Clean 🧼 contextual options list source block

Paragraph Take the opportunity to clean up the list of options by prioritizing them and grouping related actions. source block

Paragraph Remove options that don’t make sense. This list shouldn’t become a “dumping ground” for options that we don’t know where else to place 🗑️🗑️ source block

Paragraph "All documents" do not need to be here since we have the doc. browser. Remember the UX principle of keeping actions in one place rather than duplicating them across multiple locations. source block

Paragraph "Subdocuments" Since we have the doc. browser we can remove this. The way it looks when you click is really weird UX. source block

Paragraph Why we have "Hide Fragment citations"?. source block

Paragraph Reconsider where Attributes belongs; its current placement doesn’t feel UX-friendly. source block

Original link/embed source block