Connect a workspace to an AI and it gets that workspace: its memory, its working files, its skills and its schedules. It does not get the other workspaces, the accounts you connected somewhere else, or a teammate’s tools. GBrain shows what it is about to hand over before you press Connect, and the connection can be changed or ended afterwards.
The connect screen asks three things
Which workspace. An AI connects to one workspace. With several, GBrain asks which. With one, it goes straight to the next screen.
What it may do in the workspace. Memory and Schedules, each set to Off, Read or Full. Both start on Read.
Whether the tools you added come along. One switch, On or Off, on the row called Your tools in the workspace’s name. It starts On.
What Read and Full each hand over
| Read | Full | |
|---|---|---|
| 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 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. |
Read covers the tools that look things up. Full adds the ones that change things.
Full on either row reaches furthest. 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, teammates’ tools included, it spends the workspace’s credit, and it keeps running after the connection ends. Leave both on Read unless the AI is meant to change the workspace.
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.
The tools you added come along only while the switch is On
The tools in a workspace are the accounts and applications you added to it: a Gmail account, a Calendar and Drive, a Stripe or Sentry connection. The row lists them by name.
- Only yours. A connection acts as one person, so an AI you connect can use the tools you added to the workspace and never a teammate’s. That is also why the screen does not list theirs.
- At the level already set. The connect screen has no Read or Full for tools. What each may do is set where it was added, on the workspace’s Integrations page or on the client it came from, and the AI cannot raise it. Whatever that level allows, the AI can do as you: Gmail at Full includes sending mail.
- As you. A call that uses your Gmail runs as you and is recorded as yours.
- All or none. The switch covers every tool on the row, for that connection. Keeping one tool from one AI means taking it out of the workspace.
- The ones you add later too. A tool you add to the workspace after you connected is there the next time the AI asks, with nothing to set up again. A tool you take out is gone the same way.
Turn the switch Off and the AI gets the workspace’s memory and schedules, and none of the tools.
What a connection never carries
- The other workspaces, including one you shared into this one.
- Accounts you connected somewhere other than this workspace, unless you shared them into it.
- GBrain’s web search and page reading.
- A teammate’s tools.
- A chat thread, directly. No tool an AI can call opens a thread. What the workspace filed from a conversation is memory, and Read returns memory, so a skill that saves transcripts to memory makes them readable the same way.
A change in the workspace reaches the AI at its next call
An AI reads the workspace as it is at each call. Take one of the tools out of the workspace and the AI loses it at its next call. Add one while the switch is On and the AI can use it. To keep a new tool from an AI, turn the switch Off on the connection first.
Every call is on the Activity page
A call that used one of the tools says which connection made it, as in via ChatGPT on Hex, and it also shows on that connection’s own page under Activity. 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 Clients, pick the connection, and open Change what it reaches. A connection is named for the AI and the workspace, like ChatGPT on Hex. Memory and Schedules have their rungs there, and the tools have their switch. A change applies from the AI’s next call.
To end a connection, delete it. New calls stop at once, and a call already running finishes. Scheduled work the AI created keeps running, and the notes and files it wrote stay.
A connection lasts 30 days unless you give it more time from its page, and one that goes two weeks without a call ends too. 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.
The screen shows where approving sends you
The name on the screen is the app’s own choice. The screen also says where the approval goes, as in “Approving sends you back to chatgpt.com”, and an app running on the same computer, like Claude Code, says so instead. If the name and the address do not belong together, press Cancel.
When an AI says it cannot see something
If ChatGPT cannot see an email account in a workspace, one of these is true: the switch is Off on its connection, the account is not in the workspace, the account is switched off there, it belongs to a teammate, or Google needs a fresh sign-in. Turn the switch On from Change what it reaches, or add the account on the workspace’s Integrations page.
Codex and Cursor take a token
Codex and Cursor take a token instead of signing in. GBrain sets them up from the workspace with the tools Off, at one level for both Memory and Schedules, so Read and write means Schedules at Full. The connection is named for the AI, like Codex CLI, and a second workspace gets its own, like Codex CLI on Hex. Turn the tools on from Change what it reaches.
If you already have a client of that name that holds other applications, GBrain leaves it exactly as it is and makes the AI a new connection of its own, so the AI reaches the workspace and nothing on your client.
Connect one from the Connect an assistant page. The accounts a workspace can hold are on Applications, and the ladder each level sits on is on Permissions.