Workspaces: overview

• Connections — each integration authorisation belongs to exactly one workspace.
• Workspace memory — durable shared context for that workspace only.
• Conversations — Ask history scoped to the workspace and your account.
• Members and roles — who can read what inside the workspace.
• Usage — credits and limits counted per workspace.

1. 1Open the workspace switcher.
2. 2Select the target workspace and confirm the change.
3. 3Start a new conversation if the previous one belongs to a different workspace.
4. 4Re-run your question so results come from the new workspace.

• Every request resolves an explicit workspace identity before any data is read.
• Queries are filtered by workspace, so a record cannot be returned by omission.
• Connections and memory are looked up within the resolved workspace only.
• Failures are closed: if a workspace cannot be resolved, the request is denied rather than defaulted.

• One workspace per business or client when data must not mix.
• A shared team workspace when collaboration matters more than separation.
• Separate workspaces for separate legal entities or currencies.
• Fewer workspaces than you think — every switch is a chance to run a question in the wrong context.

Name a workspace after the thing it protects, not the team that uses it: "Northwind — Finance", not "Sam's workspace". Names appear in the switcher during every question, so a clear name is a real safety control.