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

# User Management

User Management is part of Infraon Configuration and is accessible by administrators and authorized users. It involves managing users and defining their role and access level across modules of Infraon.

Infraon's User Management module consists of six additional modules.

They are:

**Users:** Invite new users or edit/delete existing users.

**Roles & Privileges:** Create new roles or edit/delete existing roles and define privileges for roles.

**Requesters:** Create special accounts for end-users to raise Incident or Change requests.

**Teams:** Create teams of users with similar skills to assign tasks to easily enable collaboration and mutual support.

**Department:** Create departments, assign team members, and align them with managers.

**Password Policy:** Create a password policy to enhance security and meet compliance standards.

**My Leave:** View and apply for leave of absence from work.

**Leaves:** View Holiday List and leave categories as per organizational policy.

Let's see each of these in detail. 


---

# 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.infraon.io/infinity/user-guide/infraon-configuration/user-management.md?ask=<question>&goal=<user_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.