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 (auto-created at signup)
├── Members
│   ├── Owner (you)
│   ├── Admins
│   ├── Developers
│   └── Viewers
├── Workspaces
│   ├── Default Workspace (auto-created)
│   └── Additional Workspaces
├── Billing & Subscription
└── BYOK Configuration (optional)

​
Relationship with Workspaces

AspectOrganizationWorkspace
CreationAuto-created at signupCreated manually
BillingCentralized subscriptionInherits from organization
MembersAll team membersSubset with workspace access
Cloud ProviderN/ASingle provider per workspace
ResourcesShared quota poolIsolated agents, connections, KBs

Learn More About Workspaces

Create and manage workspaces within your organization

​
Accessing Organization Settings

Navigate to your organization settings from the Organizations page or use the quick access icons in the workspace selector.
Organization section showing settings, members, subscription, and BYOK icons

​
Quick Access Icons

IconTabDescription
⚙️ SettingsGeneralEdit organization name and description
👥 UsersMembersManage team members and invitations
💳 CardSubscriptionView billing and usage (Owner only)
🔑 KeyBYOKConfigure AWS Bedrock credentials (Owner only)

​
Organization Settings

​
General Settings

Edit your organization’s basic information:

Organization Name

Naming Guidelines: - Choose a clear, descriptive name - Include team or company identifier - Examples: “Acme Corp”, “Platform Team”, “My Projects”

Description

Best Practices: - Describe the organization’s purpose - Note the primary team or use case - Keep it concise and informative
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

Click the Members icon (👥) on your organization card
2

Click Invite Members

Click the Invite Members button in the members panel
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

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

PermissionOwnerAdminDeveloperViewer
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

ActionHow To
Change RoleClick the role dropdown next to a member and select a new role
Edit Workspace AccessClick the grid icon to manage which workspaces a Developer/Viewer can access
Remove MemberClick the trash icon and confirm removal
Resend InvitationFor pending invitations, click the refresh icon
Cancel InvitationFor pending invitations, click the X icon
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

Plan Overview

Subscription Details - Current plan and features - Billing cycle information - Payment method management - Upgrade/downgrade options

Usage Tracking

Monitor Consumption - Credit usage across all workspaces - Member count vs. limit - Workspace count vs. limit - Usage trends over time

​
Member Limits

Your subscription plan determines how many members you can have:
  • Starter Plan: Limited members (check your plan details)
  • Advanced Plan: Unlimited members
The member count includes both active members and pending invitations.

​
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