> 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/department.md).

# Department

Departments are created within Infraon to group users logically to suit the organization's requirements. Assigning departments to help align teams to workflows, assigning tickets and tasks, and prioritizing work.&#x20;

In short, departments are added for efficient work assignment and team management.&#x20;

Users can be part of multiple departments at the same time.&#x20;

## **Add Department**&#x20;

Click on the **'Add Department'** button in the top right corner. Provide a department name, select a department head and a prime user, and save.&#x20;

> \***Department Head** - Can be managers or business owners who are decision-makers or otherwise known as high-level approvers.&#x20;

> \***Prime User** - can be team leads or a senior member of the team who is in charge of the allocation of work. They are the primary responsibility owners and have basic approval privileges too.&#x20;

### **Instructions to 'Add a Department'**&#x20;

* Go to Infraon Configuration -> User Management -> Department&#x20;
* Click on the 'Add Department' button.&#x20;

<table data-header-hidden><thead><tr><th width="190"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong> </td><td><strong>Action</strong> </td><td><strong>Description/Example</strong> </td></tr><tr><td>Department Name* </td><td>Give a name to your Department's password policy. </td><td>Incident Management, Finance, HR, etc. </td></tr><tr><td>Department Head </td><td>Select a user using the dropdown menu to make them the department's head. </td><td>Department Heads can be managers or business owners who are decision-makers. They are otherwise known as high-level approvers. </td></tr><tr><td>Prime User </td><td>Select user(s) using the dropdown menu to make them the department's head. </td><td><p>Prime User(s) can be team leads or a senior member of the team who is in charge of allocating work. </p><p>They are the primary responsibility owners and have basic approval privileges too. </p></td></tr><tr><td>Description </td><td>Add a brief description of the department. </td><td>Handles tickets, Manages payroll and taxation, For new hire onboarding, etc. </td></tr></tbody></table>

Once all the parameters are added, click 'Submit' to save the department.&#x20;

Repeat the process to add multiple departments.  Departments can be edited or deleted using the respective icons.


---

# 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/department.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.
