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

# Map an existing group (Advanced)

This page maps a GDAP role to a security group that already exists in your partner tenant, rather than creating one. Use it when your groups do not follow the `M365 GDAP RoleName` naming convention, for example when bringing an existing GDAP setup into CIPP. For everything else, build a [Role Templates](/user-documentation/tenant/gdap-management/role-templates.md) - it creates and maps the groups for you.

Select a group and a role, then use the add button to build up the list of mappings. Each pairing appears in the Role Mappings table below, where it can be removed again before you submit.

| Field            | Description                                        |
| ---------------- | -------------------------------------------------- |
| Select Group     | An existing security group in your partner tenant. |
| Select GDAP Role | The role to assign through that group.             |

{% hint style="warning" %}
This is an advanced page. Use extreme caution. The following limitations apply:

* Reserved groups and roles are unavailable for mapping, to prevent misconfigurations due to permission overlap.
* Only one role can be mapped per group. If your current configuration maps more than one, use the **Reset Role Mapping** action on the relationship.
* Certain roles may not be compatible with GDAP. See the [Microsoft documentation](https://learn.microsoft.com/en-us/partner-center/customers/gdap-least-privileged-roles-by-task) on GDAP role guidance.
  {% 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/tenant/gdap-management/role-templates/mappings/add.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.