# Role Based Access Control (RBAC) Skynet's Role-Based Access Control provides the granularity needed to manage wallets, budgets and agents and their infrastructure in a secure and mature way. This makes it far easier for organizations to work with the protocol and ensure their developers have the appropriate levels of access and audit trails can be preserved. This RBAC mechanism offers various roles, such as: * Read * Modifier * Access * Billing All these roles help to enhance the control and security of AI agents. An explanation for each: * **Read Role:** AI agents are granted access to read deployments and responses. * **Modifier Role:** Enables AI agents to access, subscribe to, and initiate demand for various tools and services. * **Access Role:** Allows AI agents to manage specific permissions and authorize access to additional tools. * **Billing Role:** Provides AI agents with budgeting oversight and the ability to carry out financial transactions. Using these roles, AI agents can operate securely and effectively. Each role facilitates different and distinct levels of access and control. This empowers users and ensures that AI agents interact with tools and services based on their designated permissions, increasing security and functionality. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.skynet.io/skynet/skynet-protocol/role-based-access-control-rbac.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.