> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oncortex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Using multiple brains

> One connection, every brain you can access

One Cortex connection covers all the brains you can access in your workspace: your own brain plus the team brains you belong to, each at the role you hold there. You do not add a connection per brain; the agent works across them through the one connection.

## How the agent chooses

When you ask a question, the agent searches across the brains you can access, and every result says which brain it came from. When you ask it to save something, it goes to **your own brain** unless you name another: your brain is marked as yours in the list the agent sees, so it never has to guess from a name. A team or client brain is written only when you say so, for example *"save this client info"* or *"file this in the compliance brain"*, and the agent confirms the first time in a conversation. If nothing is marked as your brain, the agent asks before its first write. The agent names the destination brain explicitly either way. If you can write to only one brain, that is the natural destination; if you can write to several, the agent picks from your brains by name and purpose, which is why clear brain names and descriptions matter.

You can always direct it yourself: *"search the team handbook"*, *"file this in my work brain"*. The agent sees your brain list, with your role on each, so plain references like these resolve reliably.

## Can my agent write somewhere it shouldn't?

The agent acts as you, so it is bound by your roles, checked live on every call. It cannot write to a brain you can only read, and it cannot see a brain you are not a member of at all. Asked to do something outside your access, it gets a clear refusal that points at the legitimate route, such as asking a brain owner for a role.

Within your access, the agent does what you tell it. If you would rather draft privately and share deliberately, keep your own brain as the working surface and use [promoting](/brains/promoting) to move finished knowledge into shared brains; that keeps the private-first habit with no extra setup.

## More than one workspace

A connection belongs to one workspace. If you work in two workspaces, say your company and a client's, add one connection for each; the agent then has two Cortex connections, clearly named, each acting as you in its own workspace. Brains never span workspaces, so there is no way for content to drift between them.

## Try it

1. With one connection set up, ask your agent *"what brains can you see, and what's your role on each?"*.
2. Ask a question you know is answered in a team brain, and notice the answer says which brain it came from.
3. Ask it to save a note "in my work brain", then check the page arrived there and nowhere else.