> ## 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 and manage your cloud operations workspaces

Create and manage your cloud operations workspaces. Workspaces are the foundation of your CloudThinker environment, providing isolated environments for different teams, projects, or cloud infrastructures.

## Overview

Workspaces in CloudThinker provide:

* **Isolated Environments**: Separate cloud operations for different teams or projects
* **Multi-Cloud Support**: Choose your preferred cloud infrastructure provider
* **Team Collaboration**: Manage users and access within each workspace
* **Resource Organization**: Keep agents, [connections](/guide/connections/overview), and [knowledge bases](/guide/knowledge) organized
* **Flexible Management**: Create multiple workspaces for different use cases

<Card title="Create New Workspace" icon="plus" href="#creating-workspaces">
  Set up a new workspace for your cloud operations
</Card>

<Info>
  Workspaces exist within your [Organization](/guide/organization). Every user
  gets a default organization and workspace at signup. Billing and member
  management happen at the organization level, while workspaces provide isolated
  environments for your cloud operations.
</Info>

***

## Creating Workspaces

New workspaces are created within your organization. Only organization Owners and Admins can create workspaces.

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

  <Step title="Click New Workspace">
    Click the "New workspace" button on your organization card
  </Step>

  <Step title="Select Cloud Provider">
    Choose your preferred cloud infrastructure provider (cannot be changed
    later)
  </Step>

  <Step title="Enter Workspace Details">
    Provide a name and description for your workspace
  </Step>

  <Step title="Create Workspace">Review and create your workspace</Step>
</Steps>

### Provider Selection

When creating a workspace, you must select a primary cloud infrastructure provider:

<CardGroup cols={3}>
  <Card title="Amazon Web Services" icon="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" color="#FF9900" width="24" height="24" data-path="images/icons/aws.svg">
    **AWS**

    Comprehensive support for EC2, S3, RDS, Lambda, and other AWS services for cloud operations and optimization.
  </Card>

  <Card title="Google Cloud Platform" icon="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" color="#4285F4" width="24" height="24" data-path="images/icons/gcp.svg">
    **GCP**

    Integration with Compute Engine, Cloud Storage, BigQuery, and Kubernetes Engine for Google Cloud operations.
  </Card>

  <Card title="Microsoft Azure" icon="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" color="#0078D4" width="24" height="24" data-path="images/icons/azure.svg">
    **Azure**

    Support for Virtual Machines, Blob Storage, SQL Database, and Container Instances for Azure cloud management.
  </Card>
</CardGroup>

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

### Workspace Configuration

<CardGroup cols={2}>
  <Card title="Workspace Name" icon="tag">
    **Naming Guidelines:**

    * Choose a clear, descriptive name
    * Include team, project, or environment identifiers
    * Use consistent naming conventions across workspaces
    * Examples: "Production AWS", "Dev Team GCP", "Security Operations"
  </Card>

  <Card title="Description" icon="file-text">
    **Best Practices:**

    * Describe the workspace purpose and scope
    * Include information about the target environment
    * Mention the primary users or team
    * Note any special configurations or requirements
  </Card>
</CardGroup>

***

## Workspace Management

### Default Workspace

Every CloudThinker account includes a default workspace:

* **Current Status**: Shows if it's your active workspace
* **Provider**: Displays the configured cloud provider
* **Description**: Basic information about the workspace purpose
* **Actions**: Access to edit, switch, or manage workspace settings

### Managing Multiple Workspaces

<CardGroup cols={2}>
  <Card title="Workspace Switching" icon="arrows-left-right">
    **Quick Access**

    * Switch between workspaces using the workspace selector
    * Each workspace maintains its own agents, connections, and settings
    * Recent workspace context is preserved
    * Seamless transition between different environments
  </Card>

  <Card title="Workspace Organization" icon="folder-tree">
    **Structure Management**

    * Organize workspaces by team, project, or environment
    * Use descriptive names and detailed descriptions
    * Regular cleanup of unused or outdated workspaces
    * Consistent configuration across similar workspaces
  </Card>
</CardGroup>

***

## Workspace Access

Workspace access is managed through your [Organization](/guide/organization). Organization members can be granted access to specific workspaces based on their organization role, with optional role overrides per workspace.

### How Access Works

<CardGroup cols={2}>
  <Card title="Organization Owners & Admins" icon="shield-check">
    **Implicit Access** - Automatically see all workspaces in the organization -
    Always have Admin-level access to all workspaces - No explicit workspace
    assignment needed
  </Card>

  <Card title="Developers & Viewers" icon="user">
    **Explicit Access Required** - Must be assigned to specific workspaces - Can
    inherit role from organization OR have a custom workspace role - Access
    managed by Owners/Admins
  </Card>
</CardGroup>

### Managing Workspace Access

To grant a Developer or Viewer access to workspaces:

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

  <Step title="Find the Member">
    Locate the Developer or Viewer you want to manage
  </Step>

  <Step title="Edit Workspace Access">
    Click the grid icon next to their name to open workspace access settings
  </Step>

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

  <Step title="Set Role (Optional)">
    For each workspace, choose "Inherit from Org" or set a specific role
    override
  </Step>

  <Step title="Save Changes">Click Save to apply the access changes</Step>
</Steps>

### Workspace Role Options

When granting workspace access to Developers or Viewers, you can choose:

| Option               | Description                                                                 |
| -------------------- | --------------------------------------------------------------------------- |
| **Inherit from Org** | Use the member's organization role (Developer → Developer, Viewer → Viewer) |
| **Admin**            | Override to Admin role for this workspace only                              |
| **Developer**        | Override to Developer role for this workspace only                          |
| **Viewer**           | Override to Viewer role for this workspace only                             |

<Info>
  Role overrides allow fine-grained control. For example, an ORG\_VIEWER can be
  given Developer access to a specific workspace where they need to run
  operations.
</Info>

### Role Inheritance Summary

| Organization Role | Default Workspace Access  | Can Override?       |
| ----------------- | ------------------------- | ------------------- |
| **Owner**         | Admin (all workspaces)    | No - always Admin   |
| **Admin**         | Admin (all workspaces)    | No - always Admin   |
| **Developer**     | Developer (assigned only) | Yes - per workspace |
| **Viewer**        | Viewer (assigned only)    | Yes - per workspace |

<Note>
  To invite new members to your organization, see [Organization
  Members](/guide/organization#organization-members).
</Note>

***

## Workspace Features

### Isolated Resources

Each workspace maintains its own set of resources:

<CardGroup cols={2}>
  <Card title="AI Agents" icon="robot">
    **Specialized Team**

    * Dedicated AI agents configured for the workspace
    * Agent customizations and instructions
    * Role-based agent access and permissions
    * Workspace-specific agent knowledge
  </Card>

  <Card title="Connections" icon="plug">
    **Infrastructure Access**

    * Cloud provider connections and credentials
    * Database connections and access
    * Service integrations and APIs
    * Secure credential management
  </Card>

  <Card title="Knowledge Bases" icon="database">
    **Organizational Knowledge**

    * Workspace-specific documentation
    * Procedures and best practices
    * Technical references and guides
    * Team collaboration on knowledge
  </Card>

  <Card title="Operations Hub" icon="hub">
    **Operational Control**

    * Access to 325+ pre-built operations
    * Custom operations and templates
    * Operation history and results
    * Performance monitoring and analytics
  </Card>
</CardGroup>

### Workspace Benefits

<Accordion title="Team Collaboration">
  **Enhanced Teamwork:**

  * Multiple users can work within the same workspace
  * Shared access to agents, [knowledge bases](/guide/knowledge), and operations
  * Collaborative knowledge building and sharing
  * Consistent operational procedures across team members

  **Communication:**

  * Agents can reference shared knowledge bases
  * Consistent responses based on team standards
  * Collaborative problem-solving with AI agents
  * Shared operation results and insights
</Accordion>

<Accordion title="Resource Organization">
  **Structured Management:**

  * Clear separation between different environments (dev, staging, prod)
  * Dedicated resources for specific projects or teams
  * Organized access to cloud infrastructure by workspace
  * Simplified resource discovery and management

  **Security:**

  * Isolated access controls per workspace
  * Separate credential management for different environments
  * Role-based access to sensitive operations
  * Audit trails per workspace for compliance
</Accordion>

<Accordion title="Scalability">
  **Growth Support:**

  * Create workspaces as teams and projects grow
  * Flexible resource allocation per workspace
  * Independent scaling of different environments
  * Easy onboarding of new team members

  **Flexibility:**

  * Different cloud providers per workspace
  * Customized agent configurations per team
  * Workspace-specific operational procedures
  * Adaptable to changing organizational needs
</Accordion>

***

## Best Practices

### Workspace Strategy

<CardGroup cols={2}>
  <Card title="Organization Structure" icon="sitemap">
    **Planning Your Workspaces**

    * **Environment-Based**: Separate dev, staging, and production
    * **Team-Based**: Different workspaces for different teams
    * **Project-Based**: Dedicated workspace per major project
    * **Cloud-Based**: Separate workspace per cloud provider
  </Card>

  <Card title="Naming Conventions" icon="tag">
    **Consistent Naming**

    * Use clear, descriptive names
    * Include environment or team identifiers
    * Follow organizational naming standards
    * Make names searchable and intuitive
  </Card>

  <Card title="Access Management" icon="users-cog">
    **Security First**

    * Follow principle of least privilege
    * Regular audit of user access and roles
    * Use appropriate roles for different users
    * Monitor workspace activity and usage
  </Card>

  <Card title="Resource Management" icon="boxes">
    **Efficient Operations**

    * Keep workspace resources organized
    * Regular cleanup of unused resources
    * Consistent configuration across similar workspaces
    * Document workspace purposes and procedures
  </Card>
</CardGroup>

### Common Workspace Patterns

<Accordion title="Environment Separation">
  **Development → Staging → Production**

  **Development Workspace:**

  * Cloud Provider: AWS (sandbox/dev account)
  * Users: Development team, QA engineers
  * Agents: Configured for development debugging and testing
  * Knowledge Bases: Development procedures, testing guidelines

  **Staging Workspace:**

  * Cloud Provider: AWS (staging account)
  * Users: QA team, DevOps engineers, select developers
  * Agents: Configured for pre-production validation
  * Knowledge Bases: Deployment procedures, staging protocols

  **Production Workspace:**

  * Cloud Provider: AWS (production account)
  * Users: DevOps team, senior engineers, operations team
  * Agents: Configured for production monitoring and incident response
  * Knowledge Bases: Production procedures, incident response playbooks
</Accordion>

<Accordion title="Team-Based Structure">
  **Platform Team → Feature Teams → Security Team**

  **Platform Team Workspace:**

  * Focus: Infrastructure, shared services, platform operations
  * Users: Platform engineers, DevOps engineers
  * Agents: Infrastructure-focused with broad cloud access
  * Knowledge Bases: Platform documentation, infrastructure procedures

  **Feature Team Workspaces:**

  * Focus: Application development, feature-specific operations
  * Users: Development team members, product managers
  * Agents: Application-focused with limited infrastructure access
  * Knowledge Bases: Application documentation, feature requirements

  **Security Team Workspace:**

  * Focus: Security monitoring, compliance, incident response
  * Users: Security engineers, compliance team
  * Agents: Security-focused with audit and monitoring capabilities
  * Knowledge Bases: Security policies, incident response procedures
</Accordion>

***

## Getting Started

<Steps>
  <Step title="Use Your Default Workspace">
    Start with the workspace auto-created at signup
  </Step>

  <Step title="Configure Connections">
    Add cloud provider connections and credentials
  </Step>

  <Step title="Set Up Agents">
    Configure AI agents for your cloud operations
  </Step>

  <Step title="Create Additional Workspaces">
    As needed, create workspaces for different environments or teams
  </Step>

  <Step title="Invite Team Members">
    Add members to your organization and grant workspace access
  </Step>
</Steps>

## Next Steps

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

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