> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/key-concepts/partners.md).

# Partners

A **Partner** is the tenant, or brand, integrating with MDI — a DTC health brand, a pharma or weight-loss company, a retailer or pharmacy, or a lab. We use "Partner" deliberately rather than "customer" or "tenant," because we think of this as a working relationship between two companies with shared goals and mutual benefit, not a one-way vendor arrangement.

That's also why Partners help shape MDI's roadmap: we take feedback and suggestions seriously when planning product improvements, and much of what ships started as a partner request. Everything in your account — Offerings, Questionnaires, Encounters, and Panel Users — exists under a single Partner, so this is the object everything else in your integration ultimately hangs off of.

### Lifecycle status

A Partner progresses through these statuses from signup to live traffic:

<table><thead><tr><th width="192.3072509765625">Status</th><th>Meaning</th></tr></thead><tbody><tr><td><code>new</code></td><td>The Partner has just been created.</td></tr><tr><td><code>onboarding</code></td><td>Initial setup is underway — accounts, contacts, and basic configuration.</td></tr><tr><td><code>integrating</code></td><td>The Partner's team is actively building against the API or configuring the white-label app.</td></tr><tr><td><code>review</code></td><td>The integration is complete and under review before go-live.</td></tr><tr><td><code>ready</code></td><td>The Partner has passed review and is cleared to go live.</td></tr><tr><td><code>live</code></td><td>The Partner is running real, billable traffic.</td></tr></tbody></table>

### Integration type

Alongside that lifecycle, each Partner also has an integration type, which describes how they connect to MDI rather than how far along they are. There are four paths to choose from:

* **`shopify`** — a Shopify app-based integration
* **`woocommerce`** — a WooCommerce plugin-based integration
* **`full-api`** — a direct, custom integration against the MDI API
* **`white-label`** — using MDI's white-label Patient App and/or Clinicians App directly

See the integration decision guide for help choosing between these.

These paths aren't mutually exclusive, either. You can combine integration types where it makes sense — for example, using the Shopify plugin alongside webhooks, or pairing the white-label apps with the API to support custom workflows that neither option covers on its own.

### Panel Users

**Panel Users** are the Partner's operational users in the Partner Portal. They manage user access, account configuration, settings, API credentials, branding, and intake content. Partner admins invite and manage Panel Users; MDI does not manage them directly.

{% hint style="info" %}
Clinician and Patient credentials do not work in the Partner Portal. The Partner Portal is for Panel Users only. Clinicians and Support Staff use the Clinicians App, and Patients use the Patient Portal.
{% endhint %}

### Support Staff

Support Staff help resolve operational issues on an Encounter — things like shipping, billing, or missing information — and typically get involved once an Encounter moves to the `Support` status.

Support Staff can be either:

* **External** — members of the Partner's team
* **Internal** — members of MDI

Whichever side they're on, the Clinicians App gives Support Staff a shared workspace for engaging directly with patients.

### Review

Clinical and intake content requires approval before it reaches patients. Whenever a Partner edits an **Offering**, **Question**, **Option**, **Rule**, or **Questionnaire**, that edit creates a pending **Review** record rather than going live immediately.

An MDI admin has to approve the Review before the change takes effect. This step exists so that MDI's medical and compliance team has a chance to look over dosage, eligibility rules, and intake questions before patients ever see them.

{% hint style="info" %}
Plan for Review turnaround time when changing Offerings or Questionnaires. These changes do not publish immediately.
{% endhint %}


---

# 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.mdintegrations.com/partner/key-concepts/partners.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.