> 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/setting-up-your-team.md).

# Setting up your team

Set up the people who configure, build, and support your MDI integration — getting the right roles in place early makes the rest of onboarding go a lot more smoothly.

### Assign an integration owner

Designate at least one engineer as the primary technical contact. This person owns the integration through launch and into ongoing operation, so it's worth picking someone who'll stick around rather than rotating the role partway through.

Your integration owner should:

* Manage Sandbox and Live credentials.
* Implement and test API calls.
* Set up and monitor webhooks.
* Coordinate technical questions with MDI support.

### Add the right Portal users

Panel Users are your staff who access the Partner Portal. These users manage other user access, general configuration, settings, and API credentials, so beyond your integration owner, it's worth adding anyone else who needs a hand in running the program day to day — a designer for branding, a business analyst for analytics, or a care coordinator who sets up and reviews offerings and intake forms.

To invite an admin:

1. Sign in to the Partner Portal as an admin.
2. Open your account's user-management settings.
3. Invite the user by email.
4. Ask the user to accept the invitation and create a login.

{% hint style="info" %}
Admin-level billing access in the Partner Portal covers your account's billing and company details — it doesn't extend to configuring Stripe processor setup or adding new pharmacy relationships. Both remain MDI-controlled: Stripe is configured by MDI admins on your behalf, and pharmacies are selected from an MDI-maintained catalog rather than added directly. See for the full breakdown of what you control versus what needs MDI sign-off.
{% endhint %}

### Use support effectively

Slack is the primary support channel during onboarding and ongoing integration work, so make sure the integration owner and relevant admins are all in your partner Slack channel from the start.

When requesting help, include:

* The environment: Sandbox or Live.
* Relevant Patient, Encounter, Offering, or request IDs.
* Relevant API URLs and payloads if any.
* Expected and actual behavior.

{% hint style="warning" %}
Note: Slack is not HIPAA compliant. Do not share patient details there. Use patient IDs only.
{% 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/get-started/setting-up-your-team.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.