> 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/get-started/onboarding-checklist.md).

# Onboarding Checklist

Use this checklist to move from account creation to live traffic. Your Partner status — visible in the Partner Portal — shows exactly which stage you're in and tells you what to focus on next.

### Lifecycle

| Status        | Meaning                                               | Next action                                             |
| ------------- | ----------------------------------------------------- | ------------------------------------------------------- |
| `new`         | Your account exists. Setup has not started.           | Understand the platform and select an integration path. |
| `onboarding`  | You are configuring your account and access.          | Add users. Configure Offerings and Questionnaires.      |
| `integrating` | Your team is building or configuring the integration. | Test the complete flow in Sandbox.                      |
| `review`      | MDI is reviewing your configuration or integration.   | Wait for approval or address feedback.                  |
| `ready`       | You have passed review.                               | Create Live credentials and complete go-live checks.    |
| `live`        | You are processing real, billable traffic.            | Monitor operations and maintain the integration.        |

{% hint style="info" %}
MDI controls status changes. Approved changes take effect after MDI approval.
{% endhint %}

### Checklist by stage

Work through the items below in order as your status advances — each stage builds on the one before it, so it's worth finishing a stage's checklist before moving to the next.

#### `new` — orient and plan

* [ ] Read [The MDI Ecosystem](/partner/get-started/the-mdi-ecosystem.md).
* [ ] Choose a path in [Integration Paths](/partner/integration-paths.md).

#### `onboarding` — configure the account

* [ ] Add technical contacts and admin users in [Setting up your team](/partner/get-started/setting-up-your-team.md).
* [ ] Configure [Offerings](/partner/key-concepts/offerings.md) and [Questionnaires & Vouchers](/partner/key-concepts/questionnaires-and-vouchers.md).
* [ ] Set up your branding in [Theme Settings](/partner/exploring-features/theme-settings.md).
* [ ] Create a Sandbox credential. Keep credentials server-side.

#### `integrating` — build and test

* [ ] Build the selected [Integration Paths](/partner/integration-paths.md) using Sandbox credentials.
* [ ] Set up your [Exploring Features](/partner/exploring-features.md).
* [ ] Test each patient flow end to end in Sandbox.
* [ ] Verify webhook delivery and error handling before review.

#### `review` — resolve approvals

* [ ] Confirm all configuration and integration work is complete.
* [ ] Address MDI feedback promptly.
* [ ] Do not treat pending clinical-content changes as live.

#### `ready` — prepare production

* [ ] Create a Live credential in **Integration** → **Credentials**.
* [ ] Complete the [Go-Live Checklist](/partner/get-started/go-live-checklist.md).
* [ ] Validate production secrets, endpoints, and webhook configuration.

#### `live` — operate reliably

* [ ] Monitor webhook failures and common errors.
* [ ] Rotate or revoke credentials when access changes.
* [ ] Use [Support Channels](/partner/troubleshooting/support-channels.md) when you need help.

### What you control vs. what needs MDI sign-off

Onboarding is mostly self-serve from the Partner Portal, but a handful of steps route through MDI staff for clinical or payment sign-off — knowing which is which up front will save you from waiting on something you could have just built yourself, or from expecting a change to go live before it's actually been reviewed.

| Area                                        | Who handles it                                                                                                      |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Offerings catalog                           | You build and edit these directly.                                                                                  |
| Questionnaires                              | You build and edit these directly.                                                                                  |
| Branding — logo, colors, email theme        | You configure this directly.                                                                                        |
| API credentials                             | You generate your own Sandbox and Live credentials.                                                                 |
| Offering / Questionnaire changes going live | Routed through a Review — typically Medical Director approval — before the change is live. Changes are not instant. |
| Stripe setup for charging patients directly | Configured by MDI admins on your behalf; this isn't self-service.                                                   |
| Pharmacy catalog                            | Maintained by MDI. You select a pharmacy from that list rather than adding a new one yourself.                      |

If something you expect to see live isn't showing up yet, check whether it's sitting in a pending Review before assuming something's broken.


---

# 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/get-started/onboarding-checklist.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.
