**Personal and work can use one GBrain sign-in and one connected AI.** They
remain separate workspaces with separate memories, each on its own hosted
server. Use separate organizations when the readers differ: everyone in an
organization can read every workspace in it. A second workspace inside the
company's organization is not a private personal workspace.

**The workspaces do not talk or sync automatically.** One AI connected to both
can search each separately and, when asked, save selected material in the other.
That shares a copy with the destination's readers. This is hosted GBrain; these
steps do not establish that one self-hosted installation can run several
isolated memories.

## One shared workspace for one audience

Start after [the personal memory works](/docs/workspace/personal-setup).
Keep the personal workspace and its organization separate.

1. Open **Organizations**, then **New organization**. Name the new organization
   for the family or company.
2. In that organization, open **Workspaces** and **Add a workspace**. Follow
   [Set up a workspace](/docs/workspace/setup). For shared chat and cloud
   schedules, choose a plan with GBrain's own AI; Personal provides neither.
   [Which AI does what](/docs/workspace/what-runs-where) explains the difference.
3. In **Members**, invite only the people who should read the shared material.
   Review invite links and domain sign-ups too: an open joining route can admit
   more than the people invited individually. [A workspace for a sensitive
   team](/docs/workspace/sensitive-teams) has the membership checklist.
4. Add one document intended for everyone in the group. Ask the shared AI to
   save it, then start a new chat and ask a question whose answer is in it.
   Open the cited note to check the answer.
5. Before connecting email or other accounts, read
   [Who may use an account](/docs/workspace/who-may-use-an-account) and
   [Connect accounts](/docs/tools/accounts). An account-use setting controls
   access to the account, not who can read material already saved in memory.

The new workspace does not inherit personal notes or connected accounts.
Members share its memory and ordinary workspace chats. There are no per-folder
permissions. Engineering, marketing and sales can share one workspace when
everyone may read the same material. HR, legal, finance or leadership need a
separate organization when the audience is smaller. The same rule applies to
family material that only some relatives should read.

Leave Slack and Telegram disconnected until their audience has been checked;
membership alone does not restrict everyone a connected chat service lets
message the workspace. Review **Settings**, then **Data protection**, before
bringing private material in.

## One explicit crossing, checked at both ends

1. Follow **Two workspaces in one AI** on
   [Connect an AI](/docs/tools/assistants) to add the shared workspace to an
   existing connection. Each workspace keeps its own Memory level.
2. Give that AI Read on the source and Read & Write on the destination for the
   intended job. Review both settings; adding a connection is not a promise of
   read-only access.
3. Ask: *“Search Personal for the holiday plan. Show the exact summary proposed
   for Family, without saving it yet.”* Replace both names with the actual
   workspaces. Review the summary for anything the destination should not read.
4. Only then ask the AI to save that approved summary to the named destination.
   Open its new note and check both workspaces' [Activity](/docs/tools/activity).

Always name the workspace: when omitted, a connected AI's request goes to the
original workspace. Later edits do not keep the two notes in sync. A workspace's
own chat and schedules do not search the other workspace; the connected AI is
doing the crossing. [How two workspaces work together](/docs/workspace/between-workspaces)
has the full boundaries.

Where enabled, **Send to a team brain** on a personal note provides a
browser-only single-note copy. [Memory](/docs/workspace/memory) explains the
confirmation and updates; the button is not available in every organization.
A [whole-workspace fork](/docs/workspace/share-a-copy) is a separate, hands-on
setup with GBrain support, not automatic synchronization.

Create the shared organization, check its members, and test one shared note
before adding more material.