Connect a workspace to an AI and it gets that workspace: its memory, its working files, its skills, its schedules, and the connectors people put in it. It does not get the workspaces you did not pick, or the accounts you connected anywhere else. This is the way to share a team’s context with whichever AI each person uses, and it comes with the workspace: nobody needs Tools for it. GBrain shows what it is about to hand over before you press Connect ChatGPT (or whichever AI it is), and the connection can be changed or ended afterwards.
The connect screen asks two things
Which workspaces. With several, tick each one the AI should reach, then press Continue. With one, there is nothing to tick.
What it may do there. Memory and Schedules, each Off, Read or Read & Write, and Tools in the workspace, Off, Mine or Everyone’s. Memory and Schedules start at Read & Write, and Tools at Everyone’s. On Personal, Memory is Off or Read & Write, with no Read: see On Personal.
Memory and Schedules
| Read | Read & Write | |
|---|---|---|
| Memory | Everything the workspace has filed: its notes, its working files, its skills, and the list of who is in the workspace with their names, emails and roles. | Everything in Read, and it can save, change and delete notes, and write, change and delete files, including the workspace’s own instructions and skills. |
| Schedules | The workspace’s scheduled work, whoever set it, and when it runs. | Everything in Read, and it can create scheduled work, run any of it now, and remove any of it. |
Saving needs Read & Write on Memory. At Read an AI can search and read, and every save it tries is refused. An AI you use to bring things in (one that files notes from your documents, mail or chats, or one you tell to remember something) needs Memory at Read & Write. Read & Write does not let the AI raise its own levels, and it does not let it confirm a note: only a person at the workspace’s own terminal confirms one.
A browser-approved AI connection can also carry a saved writer on workspaces that support attribution. That identity does not add or remove any access: the connection can do what Memory’s level allows, like any connected AI. GBrain checks the connection before each request and again before publishing a save. If the check cannot complete, the save is not published. A save already authorized may finish. Revoked connections never fall back to a shared writer. Key connections and terminals without that identity keep their existing access and say Writer unknown; Memory explains why.
At Read & Write, a browser-approved connection deletes notes one at a time, the same way it saves them. A deleted note can be brought back for 72 hours, by asking the AI to restore it. The connection never reads private notes or private facts, and everything it saves is visible to the workspace. So it cannot delete a private note, or a note that holds a private fact it cannot see. Those stay with you. It can change the rest of such a note: rewrite it, edit it, add to it, tag it. GBrain keeps the private facts exactly as they were, and refuses a save that would change or remove one.
Read & Write reaches furthest, so give it to the AIs meant to change the workspace. What an AI writes into the workspace’s files and skills shapes how the workspace answers everyone on the team. Scheduled work is done by the workspace with everything it can reach, it spends the workspace’s credit, and it keeps running after the connection ends, so an AI that only saves to memory needs Schedules at no more than Read.
Everything the workspace has filed is text the AI reads, including text that came from a web page or an email. Read on Memory is like sharing a folder of notes.
Every working file, at any size. At Read an AI can list every working file in every folder, however deep, a page of 200 at a time, and each page says how many there are in all. It reads a file up to 256 KB in one go, and a bigger one in pieces of 64 KB (up to 256 KB if it asks), each piece saying where the next one starts. If the file changes while the AI is reading it, the next piece is refused and the AI starts again from the top, so it never joins two versions of one file. A file that is not text, like a picture or a zip, can’t be read this way. Each page and each piece is a line in the workspace’s activity.
On Personal
A Personal workspace has no AI of its own, so the AI you connect is the only thing that saves to its memory. That AI decides what to save; GBrain links each save to what is already there and tidies the memory daily. An AI at Read would save nothing, so on Personal, Memory is Off or Read & Write wherever an AI connects: the approval page, a workspace’s page for an AI that takes a key, and the AI’s page under AI & Agents.
An AI connected at Read before this keeps Read until you change it. Its page says that nothing gets saved, and the workspace’s AI & Agents page names it with a Switch to Read & Write button. GBrain never changes it for you.
A Personal workspace sleeps once nobody has used it for 15 minutes, and the AI’s next call wakes it: a search of its memory, or a read or save of its working files. That first call waits while the workspace starts, which takes about a minute, and then answers as usual. While the AI keeps working, reading memory or files, the workspace stays awake.
Tools: Off, Mine or Everyone’s
The connectors in a workspace are the ones people added to it: a Gmail account, a Calendar and Drive, a Stripe or a Linear connection. The Tools row says whose are there.
| Tools | What the AI can use |
|---|---|
| Off | None of them. The workspace’s memory and schedules only. |
| Mine | The ones you added to the workspace. |
| Everyone’s | Yours, and the ones everybody else added. Where it starts. |
- A teammate’s connector runs as them. At Everyone’s, an AI you connect can use Jamie’s Linear the way Jamie’s own would, with Jamie’s access, and the record says it was your connection that asked. Jamie sees it on their Activity page too.
- Unless its owner says otherwise. Each person sets who else may use each account they added, on their Approvals page: Everyone, no approvals needed (where every account starts), Everyone, but I approve all requests, or Only me. On the second, your AI’s call waits until Jamie approves it; on Only me, your AI doesn’t see the account. Connect accounts has each setting.
- Whose copy, when two people have one. If you and a teammate both added Gmail, the AI is told both are there and names whose it means. Your own copy is the default only when it is the only one.
- At the level already set. The connect screen has no Read or Read & Write for connectors. What each may do is set where it was added, on the workspace’s Connectors page, and the AI cannot raise it. Whatever that level allows, the AI can do: Gmail at Read & Write includes sending mail.
- The ones added later too. A connector someone adds to the workspace after you connected is there the next time the AI asks, with nothing to set up again. A connector taken out is gone the same way.
To keep a teammate’s connectors from an AI, set Tools to Mine on its connection.
The manual comes with it
Every connection can also read this documentation, at no charge and with nothing to turn on. Ask your AI how to do something in GBrain — how to bring your notes in from your own computer, invite someone, connect an account, or set up a terminal — and it looks the page up instead of guessing: it searches the docs, opens the one that answers you, and gives you the link to it.
That is ours, not yours. Reading the docs reaches no account of yours and costs no credit; what it costs is the answer in your conversation, like any other answer. It changes nothing about what the AI may do in the workspace, which is the Memory, Schedules and Tools above.
What a connection never carries
- The other workspaces, including one you shared into this one.
- Accounts you connected somewhere other than this workspace.
- GBrain’s web search and page reading as your own connectors. Those reach a terminal, or an AI given a connection to your own connectors, with Tools, not a workspace connection.
- A chat thread, directly. No command an AI can call opens a thread. What the workspace filed from a conversation is memory, and Read returns memory.
A change in the workspace reaches the AI at its next call
An AI reads the workspace — its memory and its files — as it is at each call. Take a connector out of the workspace and the AI cannot use it at its next call: with the list it already holds, the call is refused. Add one while Tools is on Mine or Everyone’s and the AI can use it the next time it asks for its list, which for most is when its next session starts. When an AI sees a connector you just added has what each host does.
Every action is on the Activity page
An action says which connection took it, as in via Hex in ChatGPT, and shows on that connection’s own Activity tab. An action on a teammate’s connector also shows on their Activity, naming you. Work a schedule does later runs as the workspace, so the AI that set the schedule is not named on that work.
Change the connection or end it
Open the workspace, then AI & Agents under Integrations, and pick the AI under the workspace’s name followed by in your AIs, as in Hex in your AIs. Its page there has Memory, Schedules and Tools in the workspace, each with its levels, and gives it more time or turns it off. A change applies from the AI’s next request.
To end a connection, delete it at the foot of that page. New requests stop at once, and one already running finishes. Scheduled work the AI created keeps running, and the notes and files it wrote stay.
A connection lasts a year unless you pick less on the same page. Leaving a workspace’s organization ends every connection you had to a workspace in it, and being added back does not restore them: connect again.
A workspace that is no longer active (its trial or subscription ended, or the account that pays for it is suspended) reaches nothing. Its connections stop at once, with a refusal that names the page that keeps the workspace, and they work again when somebody keeps it.
A workspace that is busy for a moment is asked again for a few seconds before your AI hears anything. If it still cannot answer, or its machine is stopped, the refusal says how many seconds to wait (retry_after_seconds) and ends with a request id. Nothing is lost: the same call works after the wait. If you write to us about a refusal, quote its request id and we can find exactly what happened.
A connection made before Mine and Everyone’s existed had one switch for connectors. Where that switch was On, the connection is now at Everyone’s. Set it to Mine on its page if it should only reach your own.
When an AI says it cannot see something
If ChatGPT cannot see an email account in a workspace, one of these is true: Tools is Off on its connection; it is on Mine and the account is a teammate’s; the account is not in the workspace or is switched off there; or Google needs a fresh sign-in. Change Tools on the AI’s page under AI & Agents, or add the account on the workspace’s Connectors page.
A failed lookup is not one of those. If GBrain cannot read the workspace for a moment (a few seconds of database trouble is the usual cause), the AI is told the lookup failed and to ask again, and it should say it could not check rather than that nothing is connected. If an AI says a workspace has no connectors at all, ask it again before changing anything.
An AI can also ask for the whole list in one call: every connector in the workspace, with how much each one brings and whose copy it is. That answer comes from GBrain, not from the AI’s own summary, so it is worth asking for when a count matters.
Cursor takes a key
Cursor takes a key instead of signing in. Codex signs itself in over OAuth, the way Claude and ChatGPT do. GBrain sets them up from the workspace’s AI & Agents page, under Integrations, with Tools at Everyone’s, as every connection starts, at one level for both Memory and Schedules. The connection is named for the AI, like Cursor, and a second workspace gets its own, named for the workspace in the AI, like Hex in Cursor. Narrow its Tools level on its page.
Connect an AI has the steps for each AI. The accounts a workspace can hold are on Connectors, and the ladder each level sits on is on Permissions.