Account Structure (Root & Child)

root and child accounts overview when an account is first set up on amberflo, it automatically initializes with a root account and two default child accounts development and production environments these pre configured accounts provide flexibility in managing your usage of amberflo across different stages of your workflow root account the root account serves primarily for administrative tasks and overall account management its primary functions include viewing invoices and billing details directly from amberflo managing high level settings and configurations accessing all child accounts and users for consolidated visibility child accounts child accounts are designed for using amberflo’s features and interacting with its capabilities they allow you to segregate usage between different environments development account ideal for testing, integration, and pre production activities production account reserved for live operations and real usage tracking additionally, users have the flexibility to create new child accounts to suit their specific organizational needs this can be done by navigating to settings > account configurations > child accounts you can also manage and delete your child accounts in this view note that child accounts can only be created and deleted through your root account role based access control (rbac) each child account can have distinct role based access control (rbac) settings, enabling you to assign different levels of permissions to users based on their roles this ensures that access can be restricted or expanded as needed within each environment for a deeper dive into configuring rbac, refer to our rbac guide https //docs amberflo io/docs/role based access control