> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/scepman-configuration/rbac/csr-and-form-roles.md).
# CSR and Form Roles
{% hint style="info" %}
Applicable to SCEPman Certificate Master version 2.11 and above
{% endhint %}
In addition to the roles described in [Certificate Master RBAC](/scepman-configuration/rbac.md), there are some more that are not added to the Entra application by default as they might only be required in special circumstances.
These roles can be seen as a more granular concept of what the `Request.*` roles already provide while specifically granting the permissions to request certificates using a CSR or the form.
### CSR Roles
The following roles permit users to request certificates in their specific section while only being able to provide CSRs to be signed. A certificate creation through the form will not be possible.
* **Request.All.Csr**
* **Request.Client.Csr**
* **Request.CodeSigning.Csr**
* **Request.Server.Csr**
* **Request.SubCa.Csr**
* **Request.User.Csr**
### Form Roles
The form roles will allow users to create certificates using the built-in form in Certificate Master. Signing CSRs is not possible with these roles.
* **Request.All.Form**
* **Request.Client.Form**
* **Request.CodeSigning.Form**
* **Request.Server.Form**
* **Request.SubCa.Form**
* **Request.User.Form**
## Adding the Roles
All these roles can be added by running the `Complete-SCEPmanInstallation` CMDlet. This requires version 2.11 or newer of the SCEPman PowerShell module.
#### Example:
{% code overflow="wrap" lineNumbers="true" %}
```powershell
Install-Module SCEPman -Scope CurrentUser -Force
Complete-SCEPmanInstallation app-scepman-contoso
```
{% endcode %}
---
# 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.scepman.com/scepman-configuration/rbac/csr-and-form-roles.md?ask=&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.
