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

# Organizations

> Manage your CloudThinker organization settings, members, and billing

Organizations are the top-level entity in CloudThinker that groups your [workspaces](/guide/workspaces), team members, and billing under a single account. Every user automatically gets a personal organization when they sign up.

## Overview

Organizations in CloudThinker provide:

* **Centralized Billing**: Single subscription and usage quota shared across all workspaces
* **Team Management**: Invite members and assign roles across your organization
* **Workspace Container**: Create multiple workspaces within your organization
* **[BYOK](/guide/byok) Support**: Configure your own AWS Bedrock credentials at the organization level

<Info>
  Every CloudThinker user automatically receives a personal organization upon
  signup. This organization is named after you (e.g., "John's Organization") and
  serves as your default workspace container.
</Info>

***

## Organization Structure

<div style={{ border: '1px solid #2a3142', borderRadius: '10px', overflow: 'hidden', fontFamily: 'system-ui, -apple-system, sans-serif', fontSize: '13px' }}>
  <div style={{ background: '#09AAAA', padding: '8px 14px', display: 'flex', alignItems: 'center', gap: '8px' }}>
    <span style={{ fontSize: '14px' }}>🏢</span>
    <span style={{ color: '#fff', fontWeight: 700 }}>Organization</span>
    <span style={{ color: 'rgba(255,255,255,0.6)', fontSize: '12px' }}>— top-level entity, auto-created at signup</span>
  </div>

  <div style={{ display: 'grid', gridTemplateColumns: '1fr 1fr', background: '#0f1117' }}>
    <div style={{ padding: '12px 14px', borderRight: '1px solid #2a3142', borderBottom: '1px solid #2a3142' }}>
      <div style={{ color: '#64748b', fontSize: '11px', textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '8px' }}>Members</div>

      {[
                  { label: 'Owner', desc: 'Full control · billing · BYOK', color: '#f59e0b' },
                  { label: 'Admin', desc: 'Manage members & workspaces', color: '#3b82f6' },
                  { label: 'Developer', desc: 'Run operations · use agents', color: '#10b981' },
                  { label: 'Viewer', desc: 'Read-only access', color: '#8b5cf6' },
                ].map(r => (
                  <div key={r.label} style={{ display: 'flex', alignItems: 'baseline', gap: '6px', marginBottom: '5px' }}>
                    <span style={{ color: r.color, fontWeight: 600, minWidth: '72px' }}>{r.label}</span>
                    <span style={{ color: '#475569', fontSize: '12px' }}>{r.desc}</span>
                  </div>
                ))}
    </div>

    <div style={{ padding: '12px 14px', borderBottom: '1px solid #2a3142' }}>
      <div style={{ color: '#64748b', fontSize: '11px', textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '8px' }}>Workspaces</div>

      <div style={{ display: 'flex', alignItems: 'baseline', gap: '6px', marginBottom: '5px' }}>
        <span style={{ color: '#09AAAA', fontWeight: 600, minWidth: '72px' }}>Default</span>
        <span style={{ color: '#475569', fontSize: '12px' }}>Auto-created · ready to use</span>
      </div>

      <div style={{ display: 'flex', alignItems: 'baseline', gap: '6px', marginBottom: '8px' }}>
        <span style={{ color: '#64748b', fontWeight: 600, minWidth: '72px' }}>Additional</span>
        <span style={{ color: '#475569', fontSize: '12px' }}>Per team · env · cloud provider</span>
      </div>

      <div style={{ color: '#475569', fontSize: '11px' }}>Each contains: Agents · Connections · Knowledge Base · Operations</div>
    </div>

    <div style={{ padding: '12px 14px', borderRight: '1px solid #2a3142' }}>
      <div style={{ color: '#64748b', fontSize: '11px', textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '8px' }}>Billing</div>

      {['Per-seat pricing', 'Shared credit pool across workspaces', 'Owner-only access'].map(item => (
                  <div key={item} style={{ display: 'flex', alignItems: 'center', gap: '6px', marginBottom: '4px' }}>
                    <div style={{ width: '3px', height: '3px', borderRadius: '50%', background: '#09AAAA', flexShrink: 0 }} />
                    <span style={{ color: '#475569', fontSize: '12px' }}>{item}</span>
                  </div>
                ))}
    </div>

    <div style={{ padding: '12px 14px' }}>
      <div style={{ color: '#64748b', fontSize: '11px', textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '8px' }}>BYOK <span style={{ color: '#334155', textTransform: 'none', letterSpacing: 0 }}>(optional)</span></div>

      {['Bring Your Own AWS Bedrock key', 'Bypass credit system', 'Data stays in your AWS account'].map(item => (
                  <div key={item} style={{ display: 'flex', alignItems: 'center', gap: '6px', marginBottom: '4px' }}>
                    <div style={{ width: '3px', height: '3px', borderRadius: '50%', background: '#f59e0b', flexShrink: 0 }} />
                    <span style={{ color: '#475569', fontSize: '12px' }}>{item}</span>
                  </div>
                ))}
    </div>
  </div>
</div>

### Relationship with Workspaces

| Aspect             | Organization             | Workspace                         |
| ------------------ | ------------------------ | --------------------------------- |
| **Creation**       | Auto-created at signup   | Created manually                  |
| **Billing**        | Centralized subscription | Inherits from organization        |
| **Members**        | All team members         | Subset with workspace access      |
| **Cloud Provider** | N/A                      | Single provider per workspace     |
| **Resources**      | Shared quota pool        | Isolated agents, connections, KBs |

<Card title="Learn More About Workspaces" icon="building" href="/guide/workspaces">
  Create and manage workspaces within your organization
</Card>

***

## Accessing Organization Settings

Navigate to **Admin Settings** from the user menu in the top-right corner. The Admin Settings sidebar provides access to all organization management pages:

| Page                    | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| **Organization**        | Edit organization name, view stats, and manage members |
| **Workspaces**          | Create and manage workspaces                           |
| **Billing**             | View subscription and usage (Owner only)               |
| **Usage**               | Monitor credit usage and quotas (Owner only)           |
| **BYOK**                | Configure AWS Bedrock credentials (Owner only)         |
| **Identity and access** | Domain verification, SSO, and provisioning             |

<Note>Admin Settings is only visible to organization Owners and Admins.</Note>

***

## Organization Settings

### General Settings

Edit your organization's basic information:

<CardGroup cols={2}>
  <Card title="Organization Name" icon="tag">
    **Naming Guidelines:** - Choose a clear, descriptive name - Include team or
    company identifier - Examples: "Acme Corp", "Platform Team", "My Projects"
  </Card>

  <Card title="Description" icon="file-text">
    **Best Practices:** - Describe the organization's purpose - Note the primary
    team or use case - Keep it concise and informative
  </Card>
</CardGroup>

<Note>Only organization Owners and Admins can edit organization settings.</Note>

***

## Organization Members

Invite team members to collaborate within your organization. Members can be assigned to specific workspaces with role-based access control.

### Adding Members

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

  <Step title="Click Invite Members">
    Click the **Invite Members** button in the members section
  </Step>

  <Step title="Enter Email Addresses">
    Add one or more email addresses (up to 10 at a time)
  </Step>

  <Step title="Select Role">
    Choose the appropriate organization role for the invitees
  </Step>

  <Step title="Assign Workspaces (Optional)">
    Select which workspaces the new members should have access to
  </Step>

  <Step title="Send Invitations">
    Click **Send Invites** to send invitation emails
  </Step>
</Steps>

### Organization Roles

<CardGroup cols={2}>
  <Card title="Owner" icon="crown" color="#FFD700">
    **Full Control**

    * Manage all organization settings
    * Handle billing and subscription
    * Manage all members and roles
    * Access all workspaces (implicit)
    * Configure BYOK settings
    * Transfer ownership
  </Card>

  <Card title="Admin" icon="shield-check" color="#28A745">
    **Administrative Access**

    * Manage organization members
    * Create and delete workspaces
    * Access all workspaces (implicit)
    * Cannot manage billing or BYOK
  </Card>

  <Card title="Developer" icon="code" color="#17A2B8">
    **Standard Access**

    * Access assigned workspaces only
    * Use agents and run operations
    * View and use workspace resources
    * Cannot create workspaces
  </Card>

  <Card title="Viewer" icon="eye" color="#6C757D">
    **Read-Only Access**

    * View assigned workspaces only
    * Cannot modify resources
    * Cannot run operations
    * Observation and audit purposes
  </Card>
</CardGroup>

### Role Permissions Summary

| Permission                  | Owner | Admin | Developer | Viewer |
| --------------------------- | :---: | :---: | :-------: | :----: |
| Edit organization settings  |   ✓   |   ✓   |     -     |    -   |
| Manage billing/subscription |   ✓   |   -   |     -     |    -   |
| Configure BYOK              |   ✓   |   -   |     -     |    -   |
| Invite/remove members       |   ✓   |   ✓   |     -     |    -   |
| Change member roles         |   ✓   |   ✓   |     -     |    -   |
| Create workspaces           |   ✓   |   ✓   |     -     |    -   |
| Access all workspaces       |   ✓   |   ✓   |     -     |    -   |
| Access assigned workspaces  |   ✓   |   ✓   |     ✓     |    ✓   |
| Run operations              |   ✓   |   ✓   |     ✓     |    -   |

### Managing Members

| Action                    | How To                                                                       |
| ------------------------- | ---------------------------------------------------------------------------- |
| **Change Role**           | Click the role dropdown next to a member and select a new role               |
| **Edit Workspace Access** | Click the grid icon to manage which workspaces a Developer/Viewer can access |
| **Remove Member**         | Click the trash icon and confirm removal                                     |
| **Resend Invitation**     | For pending invitations, click the refresh icon                              |
| **Cancel Invitation**     | For pending invitations, click the X icon                                    |

<Info>
  When editing workspace access for Developers or Viewers, you can also set a
  role override per workspace. This allows a Viewer to have Developer access in
  specific workspaces, or a Developer to have Admin access where needed.
</Info>

<Warning>
  Removing a member from the organization removes them from all workspaces
  within that organization.
</Warning>

***

## Subscription & Billing

Organization Owners can manage subscription and view usage from the Subscription tab.

### Subscription Features

<CardGroup cols={2}>
  <Card title="Plan Overview" icon="credit-card">
    **Subscription Details** - Current plan and features - Billing cycle
    information - Payment method management - Upgrade/downgrade options
  </Card>

  <Card title="Usage Tracking" icon="chart-line">
    **Monitor Consumption** - Credit usage across all workspaces - Member count
    vs. limit - Workspace count vs. limit - Usage trends over time
  </Card>
</CardGroup>

### Seats and Members

Your subscription plan uses **per-seat billing** — each seat you purchase grants a credit allocation and allows one active member. You can also pre-purchase additional seats to increase your credit pool before adding members.

* **Starter**: 1 member, no seat billing
* **Pro**: No minimum seats, start with 1
* **Team**: No minimum seats, start with 1
* **Business**: Minimum 5 seats
* **Enterprise**: Minimum 25 seats

Only active members count toward seat usage — pending invitations do not consume seats.

***

## BYOK (Bring Your Own Key)

Organization Owners can configure AWS Bedrock credentials to use their own LLM quota instead of CloudThinker's shared pool.

<Accordion title="What is BYOK?">
  **[Bring Your Own Key](/guide/byok)** allows you to:

  * Use your own AWS Bedrock account for LLM calls
  * Bypass CloudThinker's credit system for LLM usage
  * Have unlimited LLM operations (based on your AWS quota)
  * Maintain data residency in your own AWS account

  BYOK is configured at the organization level and applies to all workspaces.
</Accordion>

<Card title="Configure BYOK" icon="key" href="/guide/byok">
  Learn how to set up your AWS Bedrock credentials
</Card>

***

## Best Practices

### Team Structure

<CardGroup cols={2}>
  <Card title="Role Assignment" icon="users-gear">
    **Principle of Least Privilege** - Assign Owner role sparingly (1-2 people)

    * Use Admin for team leads who need workspace management - Use Developer for
      most team members - Use Viewer for stakeholders who need visibility only
  </Card>

  <Card title="Workspace Access" icon="folder-tree">
    **Organized Access** - Admins/Owners see all workspaces automatically -
    Explicitly assign Developers to relevant workspaces - Use role overrides for
    fine-grained control per workspace - Regular access reviews for compliance
  </Card>
</CardGroup>

### Common Patterns

<Accordion title="Small Team (2-5 members)">
  **Simple Structure:** - 1 Owner (team lead or account holder) - 1-2 Admins
  (senior engineers) - Remaining as Developers - Single workspace or dev/prod
  split
</Accordion>

<Accordion title="Medium Team (5-20 members)">
  **Structured Approach:** - 1 Owner (engineering manager) - 2-3 Admins (tech
  leads) - Developers assigned to relevant workspaces - Viewers for product
  managers or stakeholders - Multiple workspaces by environment or team
</Accordion>

<Accordion title="Enterprise Team (20+ members)">
  **Governance Focus:** - 1-2 Owners (platform team leads) - Admins per team or
  department - Developers with workspace-specific access - Viewers for audit and
  compliance - Workspaces by team, environment, and project - Consider [BYOK](/guide/byok) for
  cost control
</Accordion>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Create Workspaces" icon="building" href="/guide/workspaces">
    Set up workspaces for your teams and projects
  </Card>

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