> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/access-and-permissions-overview/access-management-dashboard.md).

# Access Management Dashboard

The Admin Console section of the platform provides a **centralized way to manage users, roles, and permissions**, ensuring secure and controlled access to the platform features. This section helps administrators configure user access, enforce security policies, and customize system settings to align with their organization's needs.

![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAFSGiQTIBWtkOYVzQXi%2Fuploads%2FKoIxS4XbmSl8kHRY52ik%2Fimage.png?alt=media\&token=6faf3251-c341-4538-843c-d78759cbf2ec)

### Access Management <a href="#access-management" id="access-management"></a>

CommentGive feedback on the editorThe **Access Management** module allows administrators to control who can access different parts of the platform and what actions they can perform.CommentGive feedback on the editor

* CommentGive feedback on the editor**Employees** – View, add, and manage platform users (e.g., employees, auditors, and system operators).
* CommentGive feedback on the editor**Roles** – Define role-based access control (RBAC) to ensure users have appropriate permissions based on their responsibilities.

CommentGive feedback on the editor**Use Case:** An admin can assign a **Finance Manager** role with access to **Ledger Balances and Reports**, while a **Support Agent** might only have access to transaction inquiries.

***

**Employee & Role-Based Permissions**

CommentGive feedback on the editorEvery employee or user in the system must be assigned a **role**, which dictates their access level.CommentGive feedback on the editor

* CommentGive feedback on the editor**Admins** can create **custom roles** or use predefined templates.
* CommentGive feedback on the editorPermissions include **viewing, editing, and managing transactions, reports, or ledger entries**.
* CommentGive feedback on the editorEnsures **audit trails** and security compliance by restricting sensitive actions to authorized personnel.

**Use Case:** A **bank administrator** can create a **"Read-Only Analyst" role** for auditors, allowing them to view data but not modify transactions.\\


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.xyb.co/xyb-console/access-and-permissions-overview/access-management-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
