> 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/edit.md).

# Edit Template

Editing a role template updates the set of role mappings that future invites and onboardings will be built from. The form is the same one used to create a template, prefilled with the current name and mappings.

## Editing a Template

{% stepper %}
{% step %}

### Open the template

Selecting **Edit Template** loads the template by name and populates the form with its current role mappings.
{% endstep %}

{% step %}

### Adjust the name or mappings

Change **Template Name** to rename the template, or add and remove entries under **Select GDAP Role Mappings**. Only mappings that already exist on the roles page can be selected, and at least one is required.
{% endstep %}

{% step %}

### Save

Submitting writes the changes back. A renamed template keeps its mappings and history, as CIPP tracks the original name behind the scenes rather than creating a second template.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Editing a template does not change GDAP relationships that were created from it. To bring an existing relationship in line with an updated template, use the **Reset Role Mapping** action on the relationships page.
{% endhint %}

{% hint style="info" %}
Renaming the template named `CIPP Defaults` causes CIPP to prompt you to recreate it, since it checks for that exact name.
{% 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 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/edit.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.