Documentation Index

Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview: Sub-Accounts

Prev Next

Sub-Accounts (End-Customer / Linked Accounts) are the operational accounts within a WACM hierarchy where storage resources are created and consumed. As child accounts, Sub-Accounts sit beneath either a Control Account (enterprise model) or a Channel Account (partner model). Sub-Accounts remain logically isolated from one another while enabling centralized oversight from their parent account.

Importing Sub-Accounts into WACM

WACM automatically synchronizes accounts to import all Sub-Accounts. Sub-Accounts and all associated data created through the Wasabi Account Control API will be synchronized into the platform each night.

If you believe your accounts are not syncing correctly from the Wasabi Account Control API, contact Wasabi Support.

Control Accounts With Sub-Accounts

When linked to a Control Account, Sub-Accounts typically represent departments or business units and inherit governance policies and administrative oversight from the parent Control Account.

The Control Account can:

  • Create and organize Sub-Accounts

  • Assign and manage user roles and permissions

  • Apply governance policies across Sub-Accounts

  • Monitor usage and activity across all Sub-Accounts

  • Maintain centralized oversight and reporting

The Sub-Accounts can:

  • Generate storage usage

  • Contain buckets, users, and data

  • Operate independently from one another

This model enables centralized control while maintaining separation between operational environments.

Channel Accounts With Sub-Accounts

When linked to a Channel Account, Sub-Accounts typically represent end customers. The Channel Account provisions, manages, and monitors these accounts, with usage and billing data rolling up for aggregated visibility.

The Channel Account can:

  • Create and organize Sub-Accounts

  • Delegate access to internal users

  • Monitor usage across all Sub-Accounts

  • Provide support and administration (especially in MSP scenarios)

The Sub-Accounts can:

  • Generate storage usage

  • Contain buckets, users, and policies

  • Remain isolated from sibling Sub-Accounts

This interaction model allows partners to scale across multiple customers while maintaining segmentation and centralized oversight.