Document cover

Sharing & access

Space level: Public or Privat.

    If space is public all content is public

    If space is private, just accesible by members who are invited

Document level:

    If space is public documents are public

    If space is private, documents are private just accesible by members who has access




As a user, I want to accept the invitation to join space

As a member I want to accept the invitation to join a private document

As writer when I publish a new document I want to decide if it inherits the permissions from the parent

As a member I want to move a document an inherit permissions








What happens here?

Scenario one

    Gabo and Horacio are both Admins.

    Gabo invites Bea.

    Horacio then invites Bea too.

Because Gabo and Horacio have the same role level, the first invitation (Gabo’s) is the one that counts. When Horacio tries to invite Bea, he sees that an invitation has already been sent and is pending, and no new invitation is created. This follows the standard model used by tools like Google Docs and Figma.

If both invitations are sent at the same moment, or the second Admin had no indication that one was already sent, the system still keeps only one invitation for Bea. Two invitations never turn into two separate permissions owned by different people.

Scenario two

    Gabo and Horacio have the same role (e.g., both are Admins).

    Bea has Writer access, granted by Horacio.

    Gabo removes Bea

Since Gabo and Horacio have the same role, Gabo’s removal applies fully and Bea loses all Writer access. An earlier grant from a peer can’t override a later removal. The only way for Bea to get access back is for Horacio to invite her again, as a new, deliberate action.

Scenario three

    Gabo is an Admin.

    Bea has the Writer role individually, and is also a Writer through her membership in the TeamUx group.

Removing Bea's individual Writer role should remove all of her Writer permissions, including those she gets through groups. Individual permissions take precedence over group permissions.

@Untitled Contact @Untitled Contact does this make sense? This is a concern @Gabo Beaumont told me you have about sharing User stories.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime