> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

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

A workspace is an isolated environment inside your [organization](/guide/organization) that holds its own agents, [connections](/guide/connections/overview), and [knowledge bases](/guide/knowledge). 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.

<Steps>
  <Step title="Open your organization">
    Go to the Organizations page and find your organization.
  </Step>

  <Step title="Click New workspace">
    Click **New workspace** on your organization card.
  </Step>

  <Step title="Select a cloud provider">
    Choose the primary cloud infrastructure provider for this workspace.
  </Step>

  <Step title="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.
  </Step>
</Steps>

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

### Provider options

| Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Example services agents work with                                 |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| <img src="https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/aws.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=45d526a3e9345214c0345f277da2e829" alt="AWS logo" width="16" style={{display: 'inline'}} data-path="images/icons/aws.svg" /> **Amazon Web Services**               | EC2, S3, RDS, Lambda                                              |
| <img src="https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/gcp.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=2cc7040a8e4cd401b1c388f8b0cd6fe3" alt="GCP logo" width="16" style={{display: 'inline'}} data-path="images/icons/gcp.svg" /> **Google Cloud Platform**             | Compute Engine, Cloud Storage, BigQuery, Kubernetes Engine        |
| <img src="https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/azure.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=4be469886bf170733d0cf92af6a0cb8e" alt="Azure logo" width="16" style={{display: 'inline'}} data-path="images/icons/azure.svg" /> **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](/guide/agents)                    | Agent customizations, instructions, and workspace-specific knowledge |
| [Connections](/guide/connections/overview) | Cloud provider, database, and service credentials                    |
| [Knowledge bases](/guide/knowledge)        | 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

<Steps>
  <Step title="Open organization members">
    Go to **Admin Settings → Organization** and scroll to the Members section.
  </Step>

  <Step title="Edit workspace access">
    Find the Developer or Viewer, then click the grid icon next to their name to open workspace access settings.
  </Step>

  <Step title="Toggle workspaces">
    Check or uncheck workspaces to grant or revoke access.
  </Step>

  <Step title="Set a role and save">
    For each workspace, keep **Inherit from Org** or choose a role override, then click **Save**.
  </Step>
</Steps>

<Info>
  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](/guide/organization#organization-members).
</Info>

## 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

<CardGroup cols={2}>
  <Card title="Manage organization" icon="building-columns" href="/guide/organization">
    Configure organization settings, billing, and member management
  </Card>

  <Card title="Configure agents" icon="robot" href="/guide/agents">
    Set up AI agents for your workspace operations
  </Card>
</CardGroup>