> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/platform-administration/administration/new-access-control.md). # Access control Manage permissions on the Digibee Integration Platform. Using Digibee’s access control, the access manager can determine which users have permission to perform certain tasks on the Digibee Integration Platform. ## Users, groups and roles Digibee uses a role-based access control (RBAC) model. This model restricts access to system resources based on the roles assigned to specific groups of users. On the Digibee Integration Platform, permissions are managed by assigning **users** to **groups**. Groups, in turn, are associated with a **role**, and a role is a set of permissions. These permissions can change depending on which environment the user is in: test or production. To access the Digibee Integration Platform, users must be assigned to at least one group, and they can belong to multiple groups at the same time. You can either use Digibee’s default roles and groups, which cover the most common use cases of the Platform, or create your own groups and roles. To learn more about users, groups and roles, read the articles below: * [Users](/documentation/platform-administration/administration/new-access-control/users.md) * [Groups](/documentation/platform-administration/administration/new-access-control/access-control-groups.md) * [Roles](/documentation/platform-administration/administration/new-access-control/access-control-roles.md) ## FAQ * **Can I assign a role to a user?** Not directly. To give a user permission to perform a particular action, you must assign them to a group whose role includes permission to perform that action. * **What happens if a user is not assigned to any groups?** Users who are not assigned to any groups can only view and edit their own profiles. They cannot interact with the Digibee Integration Platform. * **What happens if I belong to a group in which I have permission to perform a certain action and to another group in which I do not?** A user’s permission is the sum of the permissions of groups they belong to. This means they will be able to perform a certain action if any group they belong to grants them permission to do so. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/platform-administration/administration/new-access-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.