Acclaim is structured around your organization and accounts .
This structure defines how data is organized and how access is controlled across your team.
Visual overview The diagram below shows how your organization relates to users , multiple accounts , and each account’s settings and data , within a compliance region for data residency.
Organization The organization is the top-level entity.
Represents your company or group
Owns all accounts, users, and configuration
Defines the scope of your environment
All activity in Acclaim occurs within an organization.
Organization accounts Organization accounts are used to structure your data and configuration.
Define how workflows, settings, and activity are grouped
Control how users access different parts of the platform
Support separation across entities, programs, or regions
Organization accounts do not hold funds .
They are used for structure and access , not balances.
Structuring organization accounts Organization accounts can be configured to match your operating model.
Common patterns include:
Per entity : separate accounts for different legal entitiesPer program : isolate activity for specific programs or lines of businessPer region : separate operations across jurisdictionsPer workflow : organize claims, commissions, or collections
This structure helps maintain clarity across operations and reporting.
Treasury accounts Treasury accounts are where funds are held and managed.
Each treasury account holds a balance in a single currency
Balances are tracked as total, available, and pending
Transactions record all movement of funds
Treasury accounts are separate from organization accounts and are used for managing money , not structuring data.
Accounts and users Users are granted access at the organization and account level.
Access can be scoped to specific organization accounts
Permissions define what actions users can perform
This allows teams to operate within defined boundaries
See Users and permissions for more details. Last modified on March 29, 2026
