Skip to main content
An organization holds team workspaces. Each workspace owns its own agents, credentials, catalogs, and members.
1

Create the organization

This creates the organization’s root workspace. Note the handle it returns — you’ll use it as the parent for teams.
2

Add team workspaces

Create one per team that owns real work, not one per project.
Let the shape of your capabilities decide the shape of your workspaces. Month-end close belongs to Finance; lead qualification belongs to RevOps. The team that owns the work should own the workspace that holds it.
3

Control who can join

OPEN, the default, lets organization members discover and join. RESTRICTED makes membership invitation-only. Use RESTRICTED for workspaces holding sensitive credentials.
4

Move between workspaces

Your active workspace is what commands use when you don’t pass --workspace. Agents you create land there.
5

See a workspace's contents

This shows the workspace hub: its agents, its members, and its model configuration.

​
Naming and handles

A workspace has a handle used in addressing. To change it:
Team handles are unique within an organization, not across all of them. Two organizations can each have a platform workspace, so a bare handle is sometimes ambiguous:
The unambiguous form is the fully qualified name, acme-corp/platform.

​
Credentials across the organization

Credentials in an org vault can be shared with every workspace, or restricted to named ones:
To see everything connected anywhere in the organization:
Both require org owner or admin. See Audit and scope org credentials.

​
Deleting a workspace

A personal workspace can’t be deleted. An organization workspace can’t be deleted while team workspaces still exist under it — remove those first.

​
Next

Invite and manage members

Add people and set their roles.

Organize and publish agents

Move agents to the team that owns the work.