Skip to main content

​
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, and knowledge bases organized
  • Flexible Management: Create multiple workspaces for different use cases

Create New Workspace

Set up a new workspace for your cloud operations

​
Creating Workspaces

1

Click Create Workspace

Navigate to the Workspaces page and click “Create Workspace”
2

Select Cloud Provider

Choose your preferred cloud infrastructure provider (cannot be changed later)
3

Enter Workspace Details

Provide a name and description for your workspace
4

Save Configuration

Review and save your workspace settings

​
Provider Selection

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

Amazon Web Services

AWSComprehensive support for EC2, S3, RDS, Lambda, and other AWS services for cloud operations and optimization.

Google Cloud Platform

GCPIntegration with Compute Engine, Cloud Storage, BigQuery, and Kubernetes Engine for Google Cloud operations.

Microsoft Azure

AzureSupport for Virtual Machines, Blob Storage, SQL Database, and Container Instances for Azure cloud management.
The cloud provider selection cannot be changed after workspace creation. Choose carefully based on your primary infrastructure.

​
Workspace Configuration

Workspace Name

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”

Description

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

​
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

Workspace Switching

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

Workspace Organization

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

​
User Management

Each workspace supports collaborative team access through user management.

​
User Roles and Access

Workspace Owner

Full Control
  • Create and delete workspaces
  • Manage all users and permissions
  • Configure workspace settings
  • Access all features and resources

Administrator

Management Access
  • Manage users and roles
  • Configure connections and agents
  • Manage knowledge bases
  • Access operations and monitoring

User

Standard Access
  • Access assigned agents and operations
  • View knowledge bases and connections
  • Execute operations within permissions
  • Collaborate on shared resources

​
Workspace Features

​
Isolated Resources

Each workspace maintains its own set of resources:

AI Agents

Specialized Team
  • Dedicated AI agents configured for the workspace
  • Agent customizations and instructions
  • Role-based agent access and permissions
  • Workspace-specific agent knowledge

Connections

Infrastructure Access
  • Cloud provider connections and credentials
  • Database connections and access
  • Service integrations and APIs
  • Secure credential management

Knowledge Bases

Organizational Knowledge
  • Workspace-specific documentation
  • Procedures and best practices
  • Technical references and guides
  • Team collaboration on knowledge

Operations Hub

Operational Control
  • Access to 325+ pre-built operations
  • Custom operations and templates
  • Operation history and results
  • Performance monitoring and analytics

​
Workspace Benefits

Enhanced Teamwork:
  • Multiple users can work within the same workspace
  • Shared access to agents, knowledge bases, 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
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
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

​
Best Practices

​
Workspace Strategy

Organization Structure

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

Naming Conventions

Consistent Naming
  • Use clear, descriptive names
  • Include environment or team identifiers
  • Follow organizational naming standards
  • Make names searchable and intuitive

Access Management

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

Resource Management

Efficient Operations
  • Keep workspace resources organized
  • Regular cleanup of unused resources
  • Consistent configuration across similar workspaces
  • Document workspace purposes and procedures

​
Common Workspace Patterns

Development → Staging → ProductionDevelopment 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
Platform Team → Feature Teams → Security TeamPlatform 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

​
Getting Started

1

Assess Your Needs

Determine how many workspaces you need and their purpose
2

Create Your First Workspace

Set up a workspace for your primary cloud environment
3

Configure Resources

Add connections, agents, and knowledge bases to your workspace
4

Configure Team Access

Set up user roles and permissions for your workspace
5

Start Operations

Begin using your workspace for cloud operations and management

​
Next Steps

Configure Agents

Set up AI agents for your workspace operations
⌘I