> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/operations/staff-roles-and-access-rights.md).

# Staff, Roles & Access Rights

**Master Data → Staff & Roles.** Staff are people who have an account to log in to the portal.

{% hint style="warning" %}
Staff and providers are two different things. **Staff** determines who can log in and what they can see. **Provider** (in the Resources menu) determines who performs bookings and earns commission. One person often needs to be registered as both.
{% endhint %}

## Roles and permissions

**Master Data → Staff & Roles.** Each role determines access per module, with three levels:

| Level           | Meaning                           |
| --------------- | --------------------------------- |
| **No access**   | The menu doesn't appear at all.   |
| **View only**   | Can open and read, cannot change. |
| **Full access** | Can create, change, and delete.   |

Common examples of how this is split:

* **Receptionist** — full access to Bookings and Customers, view only for Services, no access to Balance and Settings.
* **Branch Manager** — full access to all master data and reports, no access to Balance.
* **Owner** — full access to everything, including withdrawals.

{% hint style="info" %}
Access to the **Balance** menu means the person can request a withdrawal. Grant it only to those who genuinely have authority over finances.
{% endhint %}

## Adding staff

Fill in name, email, phone number, branch, and role. Staff receive an email to set their own password. The same email cannot be used for two accounts.


---

# 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.diro.app/en/operations/staff-roles-and-access-rights.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.