> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/engage/partners.md).

# Partners

Track ongoing relationships with the organizations you work with, including linked contacts, cross-module involvement, and per-period reporting.

The **Partners** module tracks the organizations your program works with as persistent relationships rather than one record per reporting period. A partner record carries the relationship's start and end dates, the contacts who work there, and a read-only roll-up of everywhere that partner appears across PEARS — action plans, program activities, PSE site activities, success stories, indirect activities, and custom modules.

Because a partner persists, you report on it over time through [Partner Reports](/reflect/partner-reports.md) rather than re-entering the partner each period.

## Getting Started

To access Partners, hover over the **Engage** menu in the top navigation bar and click **Partners**. The list opens filtered to **Active** partners — those with no end date.

The list shows **Name**, **Unit**, **Owner**, **Status** (Active or Ended), **Created At**, and **Last Modified At**. You can customize which columns appear, filter by partner type, unit, action plan, and creation date range, and export the results.

{% hint style="info" %}
**TIP:** Partners replaces the [Partnerships](/engage/partnerships.md) and [Coalitions](/engage/coalitions.md) modules. Organizations that still have data in those modules find them under a **Legacy** heading at the bottom of the Engage menu. See [Partnerships and Coalitions as Legacy Modules](/engage/partners/legacy-modules.md).
{% endhint %}

## Workflow

{% stepper %}
{% step %}

#### [Add a Partner](/engage/partners/add-a-partner.md)

Enter the partner's name, type, site, unit, and start date, and attach the current partnership agreement.
{% endstep %}

{% step %}

#### [Partner Permissions](/engage/partners/partner-permissions.md)

Choose who can open the full partner record, share it with specific people or units, and respond to access requests.
{% endstep %}

{% step %}

#### [Other Activities](/engage/partners/other-activities.md)

Log contributions and activities that aren't captured as interactions — donated space, volunteer hours, in-kind goods.
{% endstep %}

{% step %}

#### [View Partner Details](/engage/partners/partner-details.md)

Review the roll-ups PEARS builds for you: linked contacts and their interactions, involvement across modules, and report history.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**NOTE:** Partner records have no **Mark as Complete** step. A partner is an ongoing relationship, not a per-period record — completion happens on the [Partner Report](/reflect/partner-reports.md) instead.
{% endhint %}

## Additional Actions

* [Export](/engage/partners/export.md) — Download partner records, their other activities, and their sharing grants as an Excel workbook.
* [Migrate from Partnerships and Coalitions](/engage/partners/migrate-from-legacy.md) — Bring your legacy records into Partners.
* [Link Partners to Other Records](/getting-started/getting-started/add-partners.md) — Add a Partners section entry to an action plan, program activity, PSE site activity, success story, indirect activity, or custom module.

<details>

<summary>GLOSSARY: Partners terms</summary>

* **Partner** — An ongoing relationship with an organization, carried across reporting periods.
* **Partner type** — The category of organization, drawn from your organization's Entity Types list.
* **Active** — A partner with no end date. Setting an end date marks the partner **Ended**.
* **Linked contact** — A CRM contact associated with the partner, optionally with a role.
* **Involvement** — The read-only roll-up of modules where this partner is linked.
* **Access tier** — How much of a record a given user can see. See [Partner Permissions](/engage/partners/partner-permissions.md).

</details>