> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/active-partner-relationships-with-group-report.md).
# Active Partner Relationships with Group Report
This report offers a list of all partners with an active relationship and shows each partner's campaign and group. Read more about [Partner Groups](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md).
#### Access the report
1. From the left navigation bar, select  **\[Engage] → Reports → More Reports**.
2. Search **Active Partner Relationships w/ Group** and select the report from the list of reports.
3. View the *Column* reference table below for more information.
Column reference
| Column | Description |
| ----------- | -------------------------------------------- |
| Partner ID | Unique impact.com Id for the partner. |
| Partner | Name of the partner. |
| URL | An internet location related to the partner. |
| Campaign ID | Unique impact.com Id for the campaign. |
| Campaign | Name of the campaign. |
| Date Joined | The date the partner joined. |
| Groups | Names of the groups. |
4. Once on the report page, you can use the icons at the top-right of the page to  **\[Pin]**,  **\[Schedule]**,  **\[Download]** the report in PDF, Excel, or CSV format, or  **\[Export]** it via API.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/active-partner-relationships-with-group-report.md?ask=&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.
