Access and sharing
Decide who sees a brain, who uses it in chat and who changes its content. Access is checked again with every message.
Every brain has its own access: a handbook for the whole team, a client mandate's files only for the people who handle it. The person who created the brain and admins with access can share it.
Share a brain
Open Share
Open the brain and click Share.

Choose the scope
Choose Everyone in the workspace or Selected people only. If groups are enabled (on request), the second option is called Groups and people.
Add people or groups
Search under Add people (with groups: Add groups and people) and click the match. New entries get Can use; switch to Can edit where needed.
Save
Tick Notify people by email if you like and click Save.
A restricted brain is invisible to everyone else, name included: in the list, in chat, in projects and in agents. A group applies to its current members: whoever joins has access, whoever leaves no longer does. Single documents cannot be shared separately, and people outside the workspace never get access.
What each role may do
| Action | Can use | Can edit | Creator or admin with access |
|---|---|---|---|
| Use in chat, projects and agents, view documents, Test the Brain | yes | yes | yes |
| Add sources, edit, replace and delete documents | no | yes | yes |
| Change name, description and instructions, rebuild the overview | no | yes | yes |
| Share, Default in new chats, make data protection stricter, delete the brain | no | no | yes |
| Loosen data protection | no | no | workspace admins only |
Admins and brains
Whether admins see every brain is set by an admin under Settings › Security with Admins have access to every brain (Security: sharing). New workspaces start with "off": admins are then ordinary members, and whoever creates a brain includes them with Workspace admins in the sharing sheet, or not. When the setting is switched on, Custodos names the restricted brains it opens; both directions are recorded in the activity log.
When someone leaves the workspace
- The person's personal shares are removed; a later invitation does not bring them back.
- Their brains and documents stay.
- If a brain they created has nobody else with Can edit, it passes to the admins. The removal dialog says how many brains this affects.
Best practices
- General knowledge for everyone, sensitive material restricted. Client mandates, HR and payroll belong in their own restricted brains.
- Groups instead of individuals, where groups are enabled.
- A second person with Can edit, so the brain stays maintained when someone is away or leaves.
Frequently asked questions
The brain is restricted and she is not on the list, neither personally nor through a group. The person who created it or an admin with access can add her.
If Admins have access to every brain is off, you only see a restricted brain if its creator includes the admins or shares it with you personally.