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

<style>
  {`
    .org-structure { background: #fff; border-color: #e5e7eb; }
    .org-structure .org-grid { background: #e5e7eb; }
    .org-structure .org-cell { background: #fff; }
    .dark .org-structure { background: #0f1117; border-color: #2a3142; }
    .dark .org-structure .org-grid { background: #2a3142; }
    .dark .org-structure .org-cell { background: #0f1117; }
    `}
</style>

<div style={{ borderWidth: '1px', borderStyle: 'solid', borderRadius: '10px', overflow: 'hidden', fontFamily: 'system-ui, -apple-system, sans-serif', fontSize: '13px' }} className="not-prose org-structure">
  <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.85)', fontSize: '12px' }}>— top-level entity, auto-created at signup</span>
  </div>

  <div className="org-grid" style={{ display: 'grid', gridTemplateColumns: '1fr 1fr', gap: '1px' }}>
    <div className="org-cell" style={{ padding: '12px 14px' }}>
      <div style={{ color: '#09AAAA', fontSize: '11px', fontWeight: 700, 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: 'var(--gray-600, #4b5563)', fontSize: '12px' }}>{r.desc}</span>
                  </div>
                ))}
    </div>

    <div className="org-cell" style={{ padding: '12px 14px' }}>
      <div style={{ color: '#09AAAA', fontSize: '11px', fontWeight: 700, 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: 'var(--gray-600, #4b5563)', fontSize: '12px' }}>Auto-created · ready to use</span>
      </div>

      <div style={{ display: 'flex', alignItems: 'baseline', gap: '6px', marginBottom: '8px' }}>
        <span style={{ color: 'var(--gray-700, #374151)', fontWeight: 600, minWidth: '72px' }}>Additional</span>
        <span style={{ color: 'var(--gray-600, #4b5563)', fontSize: '12px' }}>Per team · env · cloud provider</span>
      </div>

      <div style={{ color: 'var(--gray-500, #6b7280)', fontSize: '11px' }}>Each contains: Agents · Connections · Knowledge Base · Operations</div>
    </div>

    <div className="org-cell" style={{ padding: '12px 14px' }}>
      <div style={{ color: '#09AAAA', fontSize: '11px', fontWeight: 700, 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: '4px', height: '4px', borderRadius: '50%', background: '#09AAAA', flexShrink: 0 }} />
                    <span style={{ color: 'var(--gray-600, #4b5563)', fontSize: '12px' }}>{item}</span>
                  </div>
                ))}
    </div>

    <div className="org-cell" style={{ padding: '12px 14px' }}>
      <div style={{ color: '#09AAAA', fontSize: '11px', fontWeight: 700, textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '8px' }}>BYOK <span style={{ color: 'var(--gray-400, #9ca3af)', textTransform: 'none', letterSpacing: 0, fontWeight: 400 }}>(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: '4px', height: '4px', borderRadius: '50%', background: '#f59e0b', flexShrink: 0 }} />
                    <span style={{ color: 'var(--gray-600, #4b5563)', 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:

| Field                 | Guidelines                                                                                                                    |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Organization Name** | Choose a clear, descriptive name. Include a team or company identifier. Examples: "Acme Corp", "Platform Team", "My Projects" |
| **Description**       | Describe the organization's purpose. Note the primary team or use case. Keep it concise and informative                       |

<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

| Role          | Permissions                                                                                                                                                                                       |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**     | **Full control** — manage all organization settings, handle billing and subscription, manage all members and roles, access all workspaces (implicit), configure BYOK settings, transfer ownership |
| **Admin**     | **Administrative access** — manage organization members, create and delete workspaces, access all workspaces (implicit); cannot manage billing or BYOK                                            |
| **Developer** | **Standard access** — access assigned workspaces only, use agents and run operations, view and use workspace resources; cannot create workspaces                                                  |
| **Viewer**    | **Read-only access** — view assigned workspaces only, cannot modify resources, cannot run operations; observation and audit purposes                                                              |

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

| Feature            | What you can do                                                                                               |
| ------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Plan Overview**  | Current plan and features, billing cycle information, payment method management, upgrade/downgrade options    |
| **Usage Tracking** | Credit usage across all workspaces, member count vs. limit, workspace count vs. limit, usage trends over time |

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

Minimum seats vary by plan — see [Pricing & Plans](/guide/billing/pricing) for the current per-plan seat ranges and credit allocations.

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

**Role assignment (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

**Workspace access (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

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