Organizations and workspaces
Organizations and workspaces
What an organization holds (billing, members, usage, the audit log), what a workspace holds (agents, workflows, knowledge, keys, environments), the switcher and the Settings pages.
Concept3 min readUpdated 1 November 2026
Everything you make in SentientOne lives in a workspace, and every workspace belongs to an organization. The organization is the company or team: it holds the credit balance, the people and their roles, usage reports and the audit log. A workspace is a space inside it for one team, client or project, with its own agents, workflows, knowledge, keys and environments. Every account comes with one organization, named after you, and one workspace called Default, so if you never make another, nothing changes.
What lives where
| Organization | Workspace | |
|---|---|---|
| People | Members, their organization role and the pending invitations | Which members can open it, and their workspace role |
| Money | The credit balance: packs, auto top-up, the card, history and receipts | A monthly credit limit, if you set one |
| Things you build | – | Agents (with their knowledge, tools, releases and conversations), workflows, guardrails, datasets and experiments, evaluators and review queues, alerts, connected apps, MCP servers and LLM keys |
| Keys | – | The secret API key, and each agent's widget key |
| Environments | – | The promotion path (Development, Staging, Production) and every release |
| Reports | Usage per workspace, day, type and agent; the audit log | Analytics, Tracing and Conversations for its own agents |
Nothing is shared between workspaces: an agent in one can't see another's knowledge or keys. What they share is the organization's balance.
The workspace switcher
The top of the left menu shows the organization's name over the open workspace's name. Click it to see every organization you're in, with your role in each, and the workspaces you can open, with your role there; a tick marks the open one. Below the list: New workspace (organization owners and admins), Organization settings and New organization. Choosing a workspace switches to it and opens Home. See Switch workspaces and create one.
Settings
Settings, the last item under Configure in the left menu, has three groups in a column on the left:
| Group | Pages |
|---|---|
| Workspace | General (name, description, monthly credit limit, archiving), Members and Environments, for the open workspace |
| Organization | General (name and URL name, leaving, deleting the organization), Members (people, invitations, Make owner), Workspaces (with the archived ones and Restore), Billing, Usage and Audit log |
| Account | Profile and Security: you, whichever workspace is open |
A page your role can't open is shown with a lock and the reason. Older links still work: /settings?tab=billing opens the organization's Billing page. See Settings.
Your own organization
- It was made with your account and is named after you, such as "Sam's organization". Rename it under Settings → Organization → General.
- Its first workspace is Default. It holds the organization's credit balance, so it can't be archived; it can be renamed.
- You're the organization's owner and the workspace's admin. Everything you had before organizations is in it, under the same API key.
- You can be in more than one organization: your own, and any you're invited to. See Create another organization.
- It can't be handed to someone else or deleted on its own: its balance is your account's, so it goes when you delete your account. For a team that should carry on without you, create another organization and transfer that one.
Next
- Who can do what: Roles and permissions.
- Bring people in: Invite people.
- One balance for every workspace, and limits per workspace: Credits and billing for an organization.
- How agents go from a draft to Production: How environments and releases work.
When do I need another workspace?
When a team, a client or a project should have its own agents, keys and people, paid from the same balance. Separate billing or a separate set of members needs another organization.
Did anything move when organizations arrived?
No. Your account became the owner of its own organization, and everything you had is in its Default workspace, under the same API key.
Can a workspace belong to two organizations?
No. A workspace belongs to one organization, and an agent to one workspace.
Related
Still stuck?
Email us with what you tried and any request id. A person replies.