People often have more than one workspace: a personal one and one at work, one
per client, a sensitive team's beside the company's. Each is its own memory,
with its own chats, schedules and applications, and GBrain keeps them apart.
When the work needs two at once, a person or a connected AI does the crossing,
and every crossing is on the record.

## A workspace never reads another workspace

A workspace answers from its own memory and the applications in it. Its chats,
its schedules and its replies in Slack or Telegram don't search another
workspace, and nothing it learns is copied into one. The Tools page holds
applications, like Gmail, Linear or an MCP server, and another workspace is not
one of them.

Being a member of both doesn't join them. Everyone in an organization can open
every workspace in it, and each workspace still answers only from its own
memory.

## One AI can reach both

Connect Claude, ChatGPT or another AI to several workspaces through one
connection. Tick each workspace when you connect, or add one later from the
AI's page under the second workspace's **Integrations**. [Connect an
AI](/docs/tools/assistants) has the steps under Two workspaces in one AI. The
workspaces can belong to different GBrain accounts: sign in to both on the same
browser before you add the second.

Each workspace keeps its own levels for that AI, Memory, Schedules and Tools,
set on the AI's page in that workspace. Every tool then takes a `workspace`
argument, so the AI says which memory it reads or writes, and leaving it out
means the first.

Ask it to look in one and save to the other, as in *"find what Iris knows about
Acme and save a summary to my personal workspace"*, and the AI does both, one
call at a time. Saving needs Memory at Read & Write on the workspace it saves
to. Each workspace's [Activity](/docs/tools/activity) shows the calls made in
it.

## A terminal can reach several

`gbrainio`, GBrain's command line, reaches every workspace its terminal is
turned on in, each at its own levels. `-w` names the workspace for a command,
and a command that could mean more than one stops and lists them. [Connect a
terminal](/docs/tools/terminal) has the setup.

## In Slack, each channel has one workspace that answers

One Slack can hold several workspaces: one for the company and one for each
client or team, each answering only in its own channels. A workspace of the
company that owns the Slack can also read a channel another workspace answers
in, set to Read on its Slack page, and it never answers there. It reads only
channels the person who connected it is in.

Inside one workspace, GBrain can also keep each Slack conversation to what was
said in it, so what a private channel discussed never comes up in a public
channel or a direct message. It is off until we turn it on for a workspace, so
ask us if a team needs it.

## A copy, when a group needs what another workspace knows

[Fork the workspace](/docs/workspace/share-a-copy) to give a group a snapshot
of it in a workspace of their own. The fork is taken once and never linked to
the original afterwards. For a team whose material should stay with it, see [a
workspace for a sensitive team](/docs/workspace/sensitive-teams).

## What doesn't cross

- **Applications.** An account added to one workspace is not in another until
  somebody adds it there too.
- **Connections.** An AI connected to one workspace reaches nothing in another
  until that workspace is added to its connection.
- **One question over both.** A workspace can't search two memories at once.
  Ask a connected AI to search each one.
- **Organizations.** Nothing moves between organizations on its own.