Building a good brain
One brain per audience, only current documents, clear instructions, the right access and real test questions, then answers and sources are right.
A brain is only as good as what is in it. If the 2025 expenses policy sits next to the 2026 one, the chat may quote the old amount, with a citation. Setting one up is shown in Creating a brain.
One brain per audience
Access, instructions and the data protection level apply to a whole brain. Cut brains so that all three fit every document in them:
| Brain | Content | Who can use it? | Personal data in this brain |
|---|---|---|---|
| Firm handbook | Fee schedule, expenses policy, new engagement checklist | Everyone in the workspace | Open |
| Staff | Pay policy, templates for appraisals | Selected people only | Strict |
| Engagement Holzwerk Brunner | Correspondence, contracts, accounts | Selected people only | Pseudonymise |
One big "everything" brain cannot be shared selectively, and unrelated documents compete on every question for the few passages that go to the model. Organise many brains with New folder. Folders only organise; they change nothing about access.
Only current, clean documents
- One version per document. A new file with the same name in the same brain replaces the old one automatically. With a different name, mark the old one with Mark as replaced: it stays readable but is no longer used for answers.
- A fixed name without a year ("Expenses policy.pdf") replaces itself on the next upload. A name with a year is clearer for people but needs marking by hand. Names like "Scan_0042.pdf" help nobody.
- No drafts and copies such as "Policy_v3_final_new.docx" next to "Policy_v2.docx".
- Split very long handbooks into chapters. Whatever goes past the per-file limit is not searchable, and the document shows Partly indexed. See Limits and formats.
- The digital version rather than a scan. Custodos reads scans and images only in brains set to Open.
Instructions
A brain's Instructions go with every message in which the brain is active. Write how answers should look, not what is in the brain:
Answer questions only with what is in the documents and name the section. If something is not in them, say so and refer to Lea Keller. Always give amounts in CHF.
Planning access
- Everyone in the workspace for knowledge everyone may need, Selected people only for engagements and HR topics.
- Few editors. Can edit for the one or two people responsible, Can use for everyone else.
- Groups instead of name lists. If your workspace uses groups (on request), share a brain with a group under Groups and people. Its current members always count.
- Active in chats automatically. When an admin creates a brain for everyone in the workspace, Active in new chats by default is switched on. Leave it that way for the company handbook. For anything else, switch it off, or the brain competes with the handbook in every chat.
Agents and folders never widen access. Details in Access and sharing.
The brain's data protection level
Every brain has its own level under Personal data in this brain, independent of the chats' protection level:
| Level | Suits |
|---|---|
| Open | Policies, templates, product knowledge. Passages go to the model unchanged. |
| Pseudonymise | Correspondence and documents with personal data. |
| Strict | Brains where hard identifiers such as an IBAN or an AHV number do not belong. Such documents are rejected. |
Only admins can choose a level below the workspace's standard. See Data protection in a brain.
Checking with test questions
- Collect ten questions your team really asks, such as "What is the mileage allowance?".
- Enter each one under Test the Brain and see which passages the chat would retrieve.
- Check the answer with Ask in chat and open the source.
- If the search finds nothing suitable, add a short note with Paste text, in your team's words.
Keep the questions. They are your test whenever documents change.
Keeping it current
- One person responsible, named in the brain's description.
- 15 minutes once a month: restart documents with Error using Process again, upload new versions, ask two test questions.
- Import from Google Drive or Microsoft 365 when the original is maintained there. Custodos checks such documents regularly, and at once with Refresh from source.
- Revise several documents together. Select up to 10 Office files, PDFs and texts and open them with Edit together in chat. The brain changes only when you apply them on the Changes for the Brain card. See Keeping a brain up to date.
- Clarify retention. If Retention also applies to Company Brain is on, Custodos also deletes old brain documents. See Security: retention.
Frequently asked questions
Hardly. Only the best-matching passages go to the model, not the whole brain. Processing on upload costs credits once.
The document list gives the reason. Often the brain is set to Strict and the file contains a hard identifier, or your budget is used up. If your group keeps your data in Switzerland (on request) but the workspace processes brain documents outside it, you cannot add sources.
Next steps
Building good agents
A good agent handles exactly one recurring task, has clearly structured instructions and has been tested with real cases.
Privacy day to day
What belongs in a chat, what your workspace's protection level does, when Strict or security mode fits and how to handle attachments, images and sharing.