# Roles and Users for the Reimbursement Use Case

See the [*<mark style="color:purple;">**Overview**</mark>*](/workflow-builder/introduction/overview.md) for the **Reimbursement** use case.&#x20;

As described in the **Reimbursement** workflow, we need to create 4 roles for the different levels of approval.

| Step no. | Role            | Description      |
| -------- | --------------- | ---------------- |
| 2        | Manager         | Level 1 approver |
| 3        | Department Head | Level 2 approver |
| 4        | Finance Team    | Level 3 approver |
| 5        | Finance Head    | Level 4 approver |

We will learn to create how to [<mark style="color:purple;">**create these roles**</mark>](/user-management/managing-user-roles/creating-roles.md) in the subsequent sections.

These roles need to be assigned to users. So, we will also learn to [<mark style="color:purple;">**create these users**</mark>](/user-management/managing-users/user-lists/how-to-create-users.md) and [<mark style="color:purple;">**assign roles to them**</mark>](/user-management/managing-user-roles/assigning-custom-roles-to-users.md).&#x20;

For instance, we will create a user named **John Smith** and assign them the role of **Department Head**. For more details, see [<mark style="color:purple;">**Assigning custom roles to users**</mark>](/user-management/managing-user-roles/assigning-custom-roles-to-users.md)<mark style="color:purple;">.</mark>


---

# Agent Instructions: 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.senpiper.com/user-management/roles-and-users-for-the-reimbursement-use-case.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.