As part of our Access Control Framework, Console constitutes a structured hierarchy of components designed to regulate user roles, permissions, asset access and cross-protocol To establish a robust and quantifiable approach to access governance, this framework combines:

Let's begin with an illustrative example to help simplify Console's Access Control framework for you.

At present only two roles have access-based controls: Owners and Operators.

Admins wield unrestricted access to Main Console, while operators are subject to granular limitations and restricted to Sub-Accounts. Fine-grained access Control within modules further refines permissions, while Asset-Based Controls impose constraints based on asset types, thereby injecting precise control once a Sub-Account is delegated for operation.

In another case, this is the perfect ground for a Secure Transfer Environment with the whitelisted allocation of permissions. As architects of access policies, Owners confer specific privileges upon Operators who have restricted, read-only access.

For instance, granular access controls (such as limiting transfers with upper limit and time-based thresholds) within the transfer module introduces additional depth, restricting specific actions based on predefined roles and pre-vetted contract interactions

The Access Control Framework within Console stands as a key feature for delegating access across diverse roles, modules, and assets. The mix of role-based, access policies, and asset-based permissions ensures a dynamic equilibrium between flexibility and security, substantiating a secure, collaborative and verifiable management environment.