Workspaces

Create workspaces to isolate agents, connections, and knowledge for each team, project, or environment

A workspace is an isolated environment inside your organization that holds its own agents, connections, and knowledge bases. Every account gets a default organization and workspace at signup; billing and member management happen at the organization level.

Why workspaces

• Isolation — separate environments (dev, staging, production), teams, or projects each get their own agents, credentials, and settings.
• Multi-cloud structure — each workspace targets one primary cloud provider, so you can run AWS, GCP, and Azure operations side by side in separate workspaces.
• Access control — grant members access per workspace, with optional role overrides for fine-grained permissions.
• Organized resources — agents, connections, knowledge bases, and operation history stay scoped to the workspace where they belong.

Create a workspace

Only organization Owners and Admins can create workspaces.

1. Open your organization

   Go to the Organizations page and find your organization.

2. Click New workspace

   Click New workspace on your organization card.

3. Select a cloud provider

   Choose the primary cloud infrastructure provider for this workspace.

4. Enter workspace details

   Provide a clear, descriptive name (for example “Production AWS” or “Dev Team GCP”) and a description of the workspace purpose, then create the workspace.

The cloud provider selection cannot be changed after workspace creation. Choose based on your primary infrastructure.

Provider options

Provider	Example services agents work with
Amazon Web Services	EC2, S3, RDS, Lambda
Google Cloud Platform	Compute Engine, Cloud Storage, BigQuery, Kubernetes Engine
Microsoft Azure	Virtual Machines, Blob Storage, SQL Database, Container Instances

What lives in a workspace

Each workspace maintains its own set of resources:

Resource	Scope
Agents	Agent customizations, instructions, and workspace-specific knowledge
Connections	Cloud provider, database, and service credentials
Knowledge bases	Documentation, procedures, and references agents draw on
Operations	Pre-built and custom operations, plus their run history

Switch between workspaces with the workspace selector; each workspace keeps its own agents, connections, and settings, so nothing leaks between environments.

Workspace access

Access is managed through your organization role:

Organization role	Default workspace access	Can override per workspace?
Owner	Admin on all workspaces (implicit)	No — always Admin
Admin	Admin on all workspaces (implicit)	No — always Admin
Developer	Developer on assigned workspaces only	Yes
Viewer	Viewer on assigned workspaces only	Yes

Owners and Admins see every workspace automatically. Developers and Viewers must be assigned to specific workspaces, and each assignment can either inherit their organization role or use an Admin, Developer, or Viewer override for that workspace only.

Grant workspace access

1. Open organization members

   Go to Admin Settings → Organization and scroll to the Members section.

2. Edit workspace access

   Find the Developer or Viewer, then click the grid icon next to their name to open workspace access settings.

3. Toggle workspaces

   Check or uncheck workspaces to grant or revoke access.

4. Set a role and save

   For each workspace, keep Inherit from Org or choose a role override, then click Save.

Role overrides allow fine-grained control. For example, an organization Viewer can be given Developer access to one workspace where they need to run operations. To invite new members, see organization members.

Common workspace patterns

Pattern	How to split	Typical use
Environment-based	Dev → Staging → Production	Separate cloud accounts, stricter access and incident-response knowledge in production
Team-based	Platform, feature, and security teams	Each team gets agents and knowledge bases tuned to its focus
Provider-based	One workspace per cloud provider	Keep AWS, GCP, and Azure credentials and operations apart

Whichever pattern you choose, use consistent naming across workspaces, follow least privilege when assigning access, and clean up workspaces you no longer use.

Related

Manage organization

Configure organization settings, billing, and member management

Configure agents

Set up AI agents for your workspace operations