Personal and team workspaces

• You are the only user and only need your own context.
• You are evaluating the product before involving anyone else.
• Your work is exploratory and uncommitted.

A personal workspace keeps things simple and avoids accidental sharing while you are still learning the product.

• Other people need to ask questions about the same data.
• You need shared workspace memory and team goals.
• You need role-based permissions or an audit trail of who did what.
• You are handling a business with clients whose data must stay separate.

1. 1Create one workspace per client or business.
2. 2Connect only the accounts that belong to that client.
3. 3Store client-specific memory in that workspace.
4. 4Check the switcher before every question in a client workspace.

Switch, then start a new conversation. If you need to carry a point across, restate it explicitly rather than relying on context that will not follow you.

There is no automatic merge, so plan the move before you need it. Create the team workspace, connect the accounts it needs, write the shared context into its memory, and invite members. Keep the personal workspace for genuinely personal work.

• Do not copy personal conversations into the team workspace by pasting them.
• Re-create the shared facts as workspace memory rather than as chat history.
• Decide which connections belong to the team and which stay personal.