> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/fr/web-interface/administration/configuration/system-permissions.md).

# Attributions de rôles

Accordez aux utilisateurs standards des droits d'administration limités grâce aux permissions système dans Devolutions Server, couvrant les entrées, la gestion, divers, les outils et les modules.

La section ***Attributions de rôles*** vous permet d'accorder des droits et permissions granulaires tant aux utilisateurs qu'aux administrateurs. Les attributions de rôles se déclinent en trois types : ***Espace de travail***, ***Coffre*** et ***Fournisseur PAM***. Cliquez sur ***Ajouter*** (icône +) dans le coin supérieur gauche de la page pour en créer de nouvelles. Le bouton ***Exporter*** crée un fichier `.csv` partageable.

Attribuez des rôles aux utilisateurs, aux groupes d'utilisateurs et aux applications dans la section ***Attributions***.

#### Voir aussi

* [Devolutions Academy – Configurer les permissions système](https://academy.devolutions.net/student/path/2942210/activity/4493532)


---

# 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.devolutions.net/server/fr/web-interface/administration/configuration/system-permissions.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.