> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Account & Billing

> Understand the account structures that organize SDX workspaces, teams, users, roles, billing, subscriptions, and auditability.

Account structure determines who can see resources, who can make changes, how teams collaborate, and how subscriptions and usage are organized. In Altostrat SDX, this foundation is built from workspaces, teams, users, roles, billing accounts, subscriptions, API keys, and audit logs.

```mermaid theme={null}
flowchart TD
  Workspace["Workspace"] --> Teams["Teams"]
  Teams --> Users["Users and roles"]
  Teams --> Resources["Sites, policies, workflows, and reports"]
  Workspace --> Billing["Billing accounts and subscriptions"]
  Workspace --> Audit["Audit logs"]
  Workspace --> Keys["API keys"]
```

## What to Configure First

<CardGroup cols={3}>
  <Card title="Workspaces and Organizations" icon="building" href="./workspaces-and-organizations">
    Model your operating structure so resources, teams, and customer or business boundaries are clear.
  </Card>

  <Card title="Billing and Subscriptions" icon="receipt" href="./billing-and-subscriptions">
    Review billing accounts, subscriptions, license allocation, usage, and workspace limits.
  </Card>

  <Card title="User and Team Management" icon="user-cog" href="./user-and-team-management">
    Add people, assign teams, use roles, and create notification-only users where appropriate.
  </Card>
</CardGroup>

## Recommended Setup Order

1. Confirm the workspace and organization structure.
2. Create teams around operational boundaries, such as customer, region, department, or support tier.
3. Assign roles that match each person's responsibility.
4. Review subscription and usage state before onboarding many sites.
5. Create API keys only for integrations that need them.
6. Use audit logs to review sensitive changes.

<Tip>
  Keep teams aligned with how work is actually performed. A clean team model makes policy assignment, reporting, notifications, and incident response easier to reason about.
</Tip>