Skip to main content

Accounts

Understanding accounts and how to structure your organization's resources.

Overview​

An Account is a sub-division within an organization that provides resource scoping and access control. Think of accounts as departments, projects, or environments.

What is an Account?​

Accounts provide logical separation within an organization:

  • Resource Scoping: Users and service accounts belong to specific accounts
  • Permission Boundaries: Policies are scoped to accounts
  • Flexible Organization: Structure your org however makes sense
  • Multi-Account Access: Users can belong to multiple accounts

Account Patterns​

Pattern 1: Environment-Based​

Separate accounts by deployment environment:

Organization: Acme Corp
├── Production Account
│   ├── Service Account: Production Deploy Bot
│   ├── Users: DevOps team only
│   └── Policies: Restrictive permissions
├── Staging Account
│   ├── Service Account: Staging Deploy Bot
│   ├── Users: Developers + QA
│   └── Policies: More permissive
└── Development Account
    ├── Service Account: Dev Bot
    ├── Users: All developers
    └── Policies: Very permissive

Best for: SaaS platforms, internal tools

Pattern 2: Team/Department-Based​

Organization: Acme Corp
├── Engineering Account
├── Sales Account
├── Marketing Account
└── Finance Account

Best for: Internal company usage

Pattern 3: Project-Based​

Organization: Acme Corp
├── Product A Account
├── Product B Account
└── Shared Services Account

Best for: Multi-product companies

Multi-Account Users​

Users can belong to multiple accounts simultaneously with different permissions in each.

API Reference​

See Accounts API for complete API documentation.