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

Workspaces exist within your 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.

---

Creating Workspaces

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

1. Navigate to Workspaces

   Go to the Organizations page and find your organization

2. Click New Workspace

   Click the “New workspace” button on your organization card

3. Select Cloud Provider

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

4. Enter Workspace Details

   Provide a name and description for your workspace

5. Create Workspace

   Review and create your workspace

Provider Selection

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

Amazon Web Services

AWS

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

Google Cloud Platform

GCP

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

Microsoft Azure

Azure

Support 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

---

Workspace Access

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

How Access Works

Organization Owners & Admins

Implicit Access - Automatically see all workspaces in the organization - Always have Admin-level access to all workspaces - No explicit workspace assignment needed

Developers & Viewers

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

Managing Workspace Access

To grant a Developer or Viewer access to workspaces:

1. Open Organization Members

   Go to your organization settings and open the Members tab

2. Find the Member

   Locate the Developer or Viewer you want to manage

3. Edit Workspace Access

   Click the grid icon next to their name to open workspace access settings

4. Toggle Workspace Access

   Check/uncheck workspaces to grant or revoke access

5. Set Role (Optional)

   For each workspace, choose “Inherit from Org” or set a specific role override

6. Save Changes

   Click Save to apply the access changes

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

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.

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

To invite new members to your organization, see Organization Members.

---

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

Team Collaboration

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

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

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

---

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

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

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

---

Getting Started

1. Use Your Default Workspace

   Start with the workspace auto-created at signup

2. Configure Connections

   Add cloud provider connections and credentials

3. Set Up Agents

   Configure AI agents for your cloud operations

4. Create Additional Workspaces

   As needed, create workspaces for different environments or teams

5. Invite Team Members

   Add members to your organization and grant workspace access

Next Steps

Manage Organization

Configure organization settings, billing, and enterprise features

Configure Agents

Set up AI agents for your workspace operations