> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/admin/access-management.md).

# Access Management

### Overview <a href="#docs-internal-guid-3a0a315a-7fff-6c72-ff68-2373eb02e805" id="docs-internal-guid-3a0a315a-7fff-6c72-ff68-2373eb02e805"></a>

Access Management is the process of controlling who can access specific resources, features, or data within a system. It ensures that only authorized users have the right level of access based on their roles or responsibilities. This helps maintain security, compliance, and operational efficiency.

**Role-Based Access Control (RBAC)**

* Role-Based Access Control (RBAC) simplifies access management by organizing users into roles that define what actions they can perform and which resources they can access. Instead of assigning permissions to users individually, permissions are granted to roles — and users inherit those permissions by being assigned to one or more roles. The more roles a user has, the broader their access across the system.
* Roles can represent job functions (like Admin, Developer, Viewer) or project-specific responsibilities, offering a flexible and scalable way to manage access.

Quick Links:

* [Users](/admin/access-management/user-management.md)
* [Policy and permissions](/admin/access-management/policy-management.md)
* [Role Management](/admin/access-management/role-management.md)
* [Groups](/admin/access-management/group-management.md)
* [Built-in Roles](/admin/access-management/role-management/in-built-roles.md)
* [Access Control Auditing](/admin/access-management/auditing-and-logging.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apica.io/admin/access-management.md?ask=<question>
```

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.