Secondbrain Teams: you share the piece, not the space.
You never open your workspace to anyone. You share one piece — a document with its branch, a recap, a board — and the other person sees it in their own account, with the permission you gave them. If you keep sharing with the same people, you build a team.
Sharing
What you can share
A document and its branch
With sub-documents, canvases, recaps, clips and files. A canvas is shared this way, inside a document: it has no share of its own.
A recap
Summary, transcript and notes. Also as a public link, which does not show the transcript.
A task board
Just as you built it: its conditions, its view and its tasks.
An Atlas person
Linked to their account, whatever concerns them reaches them.
Sharing a document
- 1Share → emailOn the document's globe, Share document → Collaborators: the email of a Secondbrain user. If it is not one, it tells you right there.
- 2Edit or ViewWith Include sub-documents (the whole tree), ticked by default, everything under the document travels too, including what you add later.
- 3It just shows upIt lands in their space — if they have several, they pick which one from the notification —, with a SHARED or VIEW badge in their tree.
Two people can type in the same paragraph at once: you see each other's cursors, it saves itself and nobody overwrites anybody. Same in a recap's summary and notes, and in the canvases of the tree.
If there is no account on the other side, turn on the Public link in the same panel: read-only, always the same address, and it stops working when you turn it off.
Teams: sharing with a group
A team is a group of people you share something with once and all of them see it. It is yours, not a workspace's: you use it from any of your spaces.
- 1Create the teamFrom your avatar, Teams & sharing → New team.
- 2Add peopleBy email, each with Edit or View.
- 3Share things with itFrom the Share button of a document, recap or board, in the With a team block.

- Whoever joins gets what the team already had; whoever leaves loses everything that came through it.
- Each person's permission is a ceiling: someone on View cannot edit even if you share for editing.
- If you are on someone else's team, you see it under You're in and can leave whenever you want.

Sharing a board
A shared board is the rule, not a snapshot: every task that meets its conditions is in, today and later. One with no conditions would show every task in the space, so sharing it asks you to confirm. You share it with Share this board, in the Tasks bar; how to build one, in Tasks.
- With edit permission, the guest edits and creates tasks and comments; with View, they only look.
- They cannot touch Atlas tags: those are the scope, and the scope belongs to the owner.
- ClickUp or Jira tasks they only edit with their own account. More detail.
Linking an Atlas person
If someone in your Atlas uses Secondbrain, you invite them from their entry with Link to a user. Once they accept, the open tasks where they are tagged or assigned reach them on their own — read-only —, and so do the documents associated with them, editable or read-only, as you choose when inviting.
One specific thing → share the piece. Everything that concerns them → link the person.
What you control
What is circulating
Teams & sharing gathers, across all your spaces, what you shared, what was shared with you and the Pending invitations. Revoking from there is immediate, and whoever received it can Remove it whenever they want.

What is not shared
A guest never sees your Atlas, your daily notes, your digest or anything that does not hang off what you shared. A team does not open anything either: it is a list of people, not a membership.
Keep reading
Shall we try it?
Create your free account and use all of this today.