> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/gestion-staffs/definir-les-droits-et-roles-des-staffs.md).

# Define the rights and roles of staff

## Define staff rights and roles

### What is this feature for?

The "Define Rights and Roles" feature allows you to structure access for each member of your team. By assigning custom roles, you can fine-tune the permissions granted to each member based on their responsibilities.

### How to access the feature?

1. Log in to Yoplanning.pro.
2. In the left menu, click on **Administration**.
3. Go to the **Configuration** section.
4. Click on **Roles**.

### Understanding Default Roles

Two roles are predefined in Yoplanning and **not modifiable**:

* **Administrator**: Full access to all features. Each team must have at least one.
* **Minimum Staff Rights**: Access only to your own sessions. This is the default role.

### Create a new custom role

1. From the "Roles" page, click the **Add** button.
2. Give your role a **meaningful name** so you can easily find it.
3. Enable or disable rights for each section of the application:
   * **Planning**: general or personal visibility.
   * **Sessions**: view, create, modify.
   * **Staffs**: visualization and administration.
   * **Team**: View/edit team information.
   * **Customers**: GDPR warning! Only grant access to the appropriate members.
   * **Products**: creation and modification.
   * **Commands**: view, create, modify.
   * **Payments**: collections, refunds.
   * **Resources**: management of material and immaterial resources.
   * **Access control**: QR code ticket scanning.
   * **Online sales**: management of reservation modules.
   * **Resellers**: Resale administration via ResaOne or third-party engines.
4. Click **Save**.

### Assign a role to a staff member

1. Go to **Administration > Staff**.
2. Click on the **three small dots** next to the relevant staff.
3. Select **Manage Rights**.
4. Choose the role from the drop-down list.

### Best practices

* Create roles based on your actual organization.
* Only give access to the customer file to people who really need it.
* Review assigned roles regularly, especially after a change in role.

### Common mistakes and solutions

* **Staff can't see some information?** → Check that the correct boxes are checked in the assigned role.
* **Too many rights granted?** → Modify or create a more restricted role and reassign it.

***

With this feature, you can structure responsibilities within your team in Yoplanning.pro in a precise and secure manner.


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/gestion-staffs/definir-les-droits-et-roles-des-staffs.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.