Sharing collections
Private, shared, and public collections — who can see what, and who can edit.
Visibility vs roles
Visibility controls who can find a collection. Roles control what members can do once they are in.
| Visibility | Who can see it |
|---|---|
| Private | Only you |
| Shared | You and accepted members (friends you invite) |
| Public | Anyone with the link can read; members can still have roles |
Warning.Preset collections cannot be shared. Visibility is locked to private.
Roles
| Capability | Viewer | Contributor | Admin | Owner |
|---|---|---|---|---|
| Read the tree | Yes | Yes | Yes | Yes |
| Add and edit items | — | Yes | Yes | Yes |
| Reorder / move / unlink | — | Yes | Yes | Yes |
| Edit collection name and settings | — | — | Yes | Yes |
| Change visibility, invite, change roles | — | — | Yes | Yes |
| Delete the collection | — | — | — | Yes |
| Leave | Yes | Yes | Yes | — |
You are the owner of collections you create. When you invite, pick contributor or admin. A collection can have up to 50 members (accepted plus pending).
Invite, accept, leave
- Add the person as a friend first — invites target friends.
- Open the collection, open sharing, and invite them as contributor or admin.
- They get a notification. They can accept or decline from the notification or the collection URL.
- Pending invites grant no access until accepted.
Members can leave a shared or public collection. Unfriending revokes membership. Soft-deleting a collection drops it out of the access chain.
Nested access
Membership on a collection applies to every nested collection under it, down to five levels. Inheritance only goes down. A private folder under a shared parent still shows as shared in the list so you are not surprised.