> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/cipp/advanced/authentication.md).

# Authentication

Authentication covers who can sign in to CIPP and what they are allowed to do: the CIPP user list, custom CIPP roles and their API permissions, the credentials of the CIPP-SAM and CIPP-SSO app registrations, and the roles and Graph permissions granted to the SAM application.

These pages are limited to users with the `superadmin` role.

{% hint style="danger" %}
As of version 8.0, users only need the \`superadmin\` role in order to access these menus and take actions. The value should be `superadmin` for self-hosted clients. Needing admin in addition to superadmin is no longer valid. Using both you will see errors. CyberDrain hosted clients should select both roles for the user on <https://management.cipp.app/>
{% endhint %}

{% hint style="warning" %}
Note that it may take some time for the role change to take effect.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/cipp/advanced/authentication.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.