Account Structure (Root & Child)

root and child accounts overview when you first create an account in amberflo, it is automatically initialized with a root account and two default child accounts development production this setup provides clear separation between environments and centralizes administrative control root account the root account is used primarily for administrative and oversight purposes its key responsibilities include viewing invoices and billing details managing global settings and configurations accessing and overseeing all child accounts and users child accounts child accounts are where amberflo’s features are actively used they allow you to separate usage and environments development for testing, integration, and pre production workflows production for live operations and tracking real usage data managing child accounts you can create additional child accounts to fit your organization’s structure to manage child accounts navigate to https //ui amberflo io/settings/account/sub accounts from here, you can create new child accounts manage existing ones delete accounts no longer needed note only the root account has permission to create or delete child accounts role based access control (rbac) each child account in amberflo can have its own rbac (role based access control) configuration, allowing for precise control over user permissions in different environments granular access control you can assign distinct roles to users within each child account, ensuring the right access for development, testing, or production environments environment specific permissions for example, a user may have administrator access in the development account but read only analyst access in production scalable security rbac ensures secure operations across teams by limiting actions based on responsibilities for detailed steps on configuring roles and permissions, see our docid\ x cprmtr7bufelamhad1q