Skip to main content
Organizations are the top-level entity in CloudThinker that groups your 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 Support: Configure your own AWS Bedrock credentials at the organization level
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.

​
Organization structure

🏢Organization— top-level entity, auto-created at signup
Members
Workspaces
DefaultAuto-created · ready to use
AdditionalPer team · env · cloud provider
Each contains: Agents · Connections · Knowledge Base · Operations
Billing
BYOK (optional)

​
Relationship with workspaces

Learn More About Workspaces

Create and manage workspaces within your organization

​
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:
Admin Settings is only visible to organization Owners and Admins.

​
Organization settings

​
General settings

Edit your organization’s basic information:
Only organization Owners and Admins can edit organization settings.

​
Organization members

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

​
Adding members

1

Open Organization Settings

Go to Admin Settings > Organization and scroll to the Members section
2

Click Invite Members

Click the Invite Members button in the members section
3

Enter Email Addresses

Add one or more email addresses (up to 10 at a time)
4

Select Role

Choose the appropriate organization role for the invitees
5

Assign Workspaces (Optional)

Select which workspaces the new members should have access to
6

Send Invitations

Click Send Invites to send invitation emails

​
Organization roles

​
Role permissions summary

​
Managing members

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.
Removing a member from the organization removes them from all workspaces within that organization.

​
Subscription & billing

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

​
Subscription features

​
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 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.
Bring Your Own Key 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.

Configure BYOK

Learn how to set up your AWS Bedrock credentials

​
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

Simple Structure: - 1 Owner (team lead or account holder) - 1-2 Admins (senior engineers) - Remaining as Developers - Single workspace or dev/prod split
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
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 for cost control

​
Next steps

Create Workspaces

Set up workspaces for your teams and projects

Configure Agents

Set up AI agents for your cloud operations