✅ As an admin, or writer I want to give access to my document(s)
Behavior from source: An admin or writer shares a document or group of documents from contextual actions on the document or preview, manages roles and access, and respects space visibility and parent-to-child permission inheritance.
Original source · exact version bafyreiakigkvlrdul5l56lka3u5hfzf6n3olxuv7ism5eybtxbohnedyce
Reviewed migration decision · Journey map · local task ID ut-383784d6790ca3a1.
Confidence: high; review status: needs-review. Similar source records are not merged. Source status icon is not a committed release or current product state.
Source acceptance and behavior
Admins and writers can share a document or group of documents through contextual actions (⋯) in the document or its preview.
Private documents support email invitations only; the stated first stage instead finds people by searching existing Seed accounts.
Public documents support email invitations and links; the stated first stage uses existing-account search and links.
In public spaces, admins can make individual documents private; documents in private spaces cannot be made public.
An invitation to a document in a private space grants access only to that document and its subdocuments.
The source says an invitation to a document in a public space grants access to the whole space, and public-space document sharing displays only people with the writer role.
Document-sharing permissions cascade to subdocuments; people invited to a parent cannot be removed from its children.
Additional people can be invited to child documents.
Admins can change roles and remove access; writers can do so except for admins.
Full original readable source 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
Paragraph Sharing access to a document on a private space source block
Paragraph In the first stage by looking for a member name who already has an account on Seed. 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
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime