> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/administration/users/tabs/authorizations.md).

# Authorizations

Authorizations correspond to the rights and permissions assigned to users or groups to access different features or modules. They allow you to precisely define who can view, create, modify, or delete data (tickets, assets, budgets, etc.). Authorizations are managed via profiles and ensure security, confidentiality, and the proper distribution of responsibilities in the management of the GLPI environment.

{% hint style="info" %}
For details on authorization, go to [profiles](/documentation/modules/administration/profiles/profiles.md)
{% endhint %}

![Authorization - Global view](/files/nA6MVU5NPw1x8ptOa95T)

{% hint style="info" %}
**Information on abbreviations**

You will be able to see in the "*profiles*" section as in the example above the letters R and D.

**R** = Recursive

This means that the profile has access to all attached child entities.

**D** = Dynamic

This means that the authorization was added through an authorization rule. If this rule is modified, the authorization will also be changed the next time the user logs in.
{% endhint %}

## Add an authorization

To add an authorization, select :

* the entity
* the profile
* the recursion

![Add authorization](/files/ezzvCS37Cz0zDrLFspZl)

## Delete an authorization

To delete an authorization use the massive action.

![delete authorization](/files/sECQ6cWcqUXxk64ahwfd)


---

# 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://help.glpi-project.org/documentation/modules/administration/users/tabs/authorizations.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.