Roles and sharing
Create a role
- In the brain, open the Sharing tab and click New role in the Roles part. A role can also be created right in an invitation: in the role picker choose + New role…, and after saving it is picked in the invitation by itself.
- Describe in a sentence or two what the role is for and click Draft with AI. The AI fills in all parts of the role from the description, the rest can be fine-tuned by hand. The description stays with the role for later edits.
- Go through the parts of the role:
- Knowledge: a folder tree. For the whole brain and for each folder, choose Hidden, Read, Propose (needs approval) or Edit. A subfolder can have more access than its parent, or be hidden.
- Skills, Agents, Connections: tick them by name, or choose all of them including new ones (All skills (also new ones) and the like). No need to deal with files.
- Storage: the tree of storage folders (contracts, invoices, images …). Whoever sees a file sees its description too.
- Start with the smallest scope. In the What the role sees preview, check what the role really sees. Watch the file names too, sometimes they reveal more than the content.
- Create role. An existing role is edited by clicking it in the Roles part.
Approving changes
- Propose on a folder means: the role may change a file, but the change gets into the brain only after approval. In folders with Edit, it changes files directly.
- A manager approves every change of the role is a shortcut for when absolutely everything should be approved.
- Approves proposals goes to a role that should decide on changes (a team lead, an editor) without managing the whole brain. It may approve only files it may edit itself.
- Proposals wait in the Changes tab. The whole proposal can be approved, or only some of its files; the rest is rejected. On the Changes tab, the author sees the state of their proposals and the reason for a rejection.
Invite a person
- Open the Sharing tab.
- Enter the e-mail, choose a role and click Send invitation.
- The invited person gets an e-mail with a link. Invitations not accepted yet can be sent again or revoked.
A person's role can be changed at any time. A new restriction applies from their next download; onlybrain cannot delete files the person downloaded earlier from their computer.
What the role affects
- Files: hidden files are not in their copy of the brain at all, not even in the history. The same goes for skills, agents and storage files the role does not have.
- Connections: the onlybrain gateway does not let through services the role does not have.
- History: for restricted roles, change descriptions are replaced with
Změna v brainu("Change in the brain") so they don't reveal hidden content. - Writing: the brain refuses a change outside the allowed folders, and a change in a folder set to Propose waits for approval.
- Documents and the map: the same rules apply.
View the brain as another role
Anyone with more rights in a brain than another role (a manager, for example) can look at the brain in the app the way that role sees it: in the brain's heading click role: and pick a role under View as role, or click View as this role on the role's card in Sharing. Files, changes, meetings and the chat then show only what the role sees.
The view is read only, nothing can be changed in it. The bar above the brain says which role the brain is shown as, and Exit brings back the own role. The view applies only to this brain and only in the open browser tab.
The role also applies to search (⌘K / Ctrl+K) and to the chat opened in a new tab: a bar above the chat says which role it answers as. Connect AI shows the role's skills, agents and recurring tasks, but connecting itself (the connector, the onlybrain app, git) always uses the own role. To connect, exit the view.
Meetings
Every role has a Meetings part on its card on the Sharing page:
- Record: may record and upload recordings.
- Sees: All meetings shared with the brain, Own and shared (own recordings and meetings shared with the person or their role), or None.
- Transcript: off means only the summary, not the full transcript.
- Edits: summarize again, rename speakers and delete. Own only, All it sees, or None; each one separately in the detailed role editor.
Without a setting: the role records where it may write the meetings folder, sees every meeting with its transcript and changes only its own. A manager sees and may do everything.
A role that does not see every meeting or their transcripts does not have the files of the meetings folder in its copy of the brain, in git, in search or in MCP. It reads the meetings it may see in the app and with the MCP tool get_meeting.
Every meeting has Who sees it: shared with the brain, or private (only its author and the managers). Chosen people and roles can be added to both. The files of a private meeting are not in the meetings folder, nobody else sees them as files and they do not go to webhooks. The choice is offered when recording too. When a meeting that was already shared becomes private, its files move, but the earlier version stays in the brain's history.
Checks
The Access tab shows who read and changed what, when and from where: the web, the onlybrain app, AI (MCP), integrations, git and onlybrain support. It filters by person, channel, kind (reads, changes, approvals, settings), path and date, and a manager can download it as CSV.
- Repeated reads of the same file by one person are merged per hour, a folder sync in the app is one entry per hour.
- The Who read it button at a file shows who read it lately.
- A member sees only their own entries. The name of a file the role does not see, or of someone else's private folder, never shows in the log.
- Every read by onlybrain support is always in the log.
Usage shows how the brain is used.
Example prompt
I need a role for an external business partner. They should read
the company information and the sales handbook, write only to outputs,
and must not see finances, internal projects or the list of other clients.
Suggest concrete path rules and explain each one.
Don't change anything, I'll check the draft in the role preview first.