> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/products/learn-card-app/referral-invitations.md).

# Referral Invitations

When an organization refers you to a partner, an invitation appears in Alerts. It names the referring organization and the partner. Choose **View Details** to review its purpose, requested data, and the organizations that would receive it.

**Accept & Connect** opens data review. Choose which data to provide and confirm the receiving organizations before connecting. Required parent approval follows the existing account permission flow.

**Decline** asks for confirmation and records your decision. **Not Now** closes details, and the close button dismisses the alert. Both leave the invitation pending. Find dismissed invitations in **Privacy & Data → Pending invitations**.

After connecting, Privacy & Data shows the receiving organizations and lets you update permissions or stop sharing. Stopping access prevents future sharing; organizations may retain copies already received. A partner's newly issued credential becomes available to those organizations after you claim it and the app synchronizes it under your permissions.

Choosing all credentials in a category includes credentials from any source in that category. Select individual credentials when you want to limit that access.

This experience appears when your app's tenant configuration and rollout flag enable referral invitations. Existing consent links and AI requests retain their existing flows.

```mermaid
flowchart TD
    A[Invitation in Alerts] --> B[View Details]
    A --> C[Accept & Connect]
    B --> C
    C --> D[Review data and receiving organizations]
    D --> E[Confirm permission]
    B --> F[Decline confirmation]
    A --> G[Dismiss alert]
    G --> H[Privacy & Data: Pending invitations]
    H --> B
    E --> I[Privacy & Data: Manage access]
```


---

# 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.learncard.com/products/learn-card-app/referral-invitations.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.