> 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/tenant/gdap-management/role-templates.md).

# Role Templates

This page lists the GDAP role templates you have created. A template is a named set of admin roles, and it is what you select when generating an invite or onboarding a tenant, so every relationship is built with a consistent set of permissions.

Each role in a template is backed by a security group in your partner tenant. CIPP creates those groups for you as you build the template, so this page is the only one you normally need: add your technicians to the groups and they gain the matching delegated access in your customer tenants.

If you have no templates yet, the page offers to create the **CIPP Defaults** template, which contains the 15 roles listed on the [Recommended Roles](/setup/maintaining-cipp/recommended-roles.md) page, or to build a custom one. If you have templates but none named `CIPP Defaults`, a warning offers to create it - so the prompt returns if you delete or rename that template.

Use **Add Template** to create a template via [Add Template](/user-documentation/tenant/gdap-management/role-templates/add.md), or **Group Mappings** to review the underlying role-to-group mappings on [Group Mappings](/user-documentation/tenant/gdap-management/role-templates/mappings.md).

## Table Details

| Column         | Description                                                                                          |
| -------------- | ---------------------------------------------------------------------------------------------------- |
| Template Id    | The name of the template. This is the value you select when creating invites and onboarding tenants. |
| Roles          | The admin roles the template grants.                                                                 |
| Group Mappings | How many security groups the template maps to.                                                       |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Edit Template</td><td>Opens <a data-mention href="/user-documentation/tenant/gdap-management/role-templates/edit.md">Edit Template</a> so you can rename it or change which roles it contains.</td><td>false</td></tr><tr><td>Clone Template</td><td>Copies the template's role mappings to a new template under a name you provide.</td><td>false</td></tr><tr><td>Create Invite</td><td>Opens the invite form with this template preselected.</td><td>false</td></tr><tr><td>Delete Template</td><td>Removes the template from CIPP. The underlying group mappings and security groups are not deleted, and existing relationships built from the template are not changed.</td><td>true</td></tr></tbody></table>

***

## 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 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.cipp.app/user-documentation/tenant/gdap-management/role-templates.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.