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

# Mappings

This tab shows how the roles approved on a GDAP relationship are actually assigned, listing each security group in your partner tenant that carries roles for the customer, and the users who are members of that group. This is where you confirm that a technician will genuinely receive the access the relationship allows, since an approved role grants nothing until it is assigned to a group and someone is a member of it.

## Table Details

| Column               | Description                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------- |
| Group - Display Name | The security group in your partner tenant that the roles are assigned through.                     |
| Status               | The current state of the access assignment.                                                        |
| Created Date Time    | When the assignment was created.                                                                   |
| Roles                | The admin roles granted in the customer tenant to members of the group.                            |
| Members              | The users in your partner tenant who are members of the group, and who therefore hold this access. |

{% hint style="info" %}
An empty table on an active relationship means the roles have been approved but never assigned to a group, so nobody holds the access yet. Use the **Reset Role Mapping** action on the relationships list to apply a role template and create the assignments.
{% 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/relationships/relationship/mappings.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.