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

# Invites

This page lists the GDAP invites that have been generated but not yet used. Each row holds the two links produced when the invite was created: one for the customer to approve the relationship, and one for a CIPP administrator to complete onboarding once it has been approved.

Use the [New Invite](/user-documentation/tenant/gdap-management/invites/add.md) button to generate more.

## Table Details

| Column         | Description                                                                                                                                             |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Timestamp      | How long ago the invite was created.                                                                                                                    |
| Row Key        | The identifier of the relationship the invite will create.                                                                                              |
| Reference      | The internal note recorded against the invite, for example a client name or ticket number.                                                              |
| Technician     | The CIPP user who generated the invite. Invites created through the API show the application name, and those created by a scheduled task show `System`. |
| Invite Url     | The link for a Global Administrator in the customer tenant to approve the relationship.                                                                 |
| Onboarding Url | The link a CIPP administrator opens to start onboarding once the invite has been approved.                                                              |
| Role Mappings  | The role mappings from the template the invite was generated with.                                                                                      |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Update Internal Reference</td><td>Sets or changes the internal note recorded against the invite.</td><td>true</td></tr><tr><td>Delete Invite</td><td>Removes the invite record from CIPP. This only deletes the entry, it does not withdraw a relationship that is already awaiting approval.</td><td>true</td></tr></tbody></table>

{% hint style="warning" %}
GDAP relationships cannot be terminated once they have reached approval pending status, so deleting an invite here removes only CIPP's record of it. The pending relationship remains in Partner Center until the customer approves it or it lapses.
{% 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/invites.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.