> 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/exploring-features/theme-settings.md).

# Theme Settings

Patients should never feel like they've left your product, even though the Patient App is technically hosted and served by MDI. Theme Settings let you brand the app and its emails at runtime, with no rebuild, no redeploy, and no engineering ticket to MDI required.

## App theming

Our theme builder lets you customize your intake form and Patient Portal experience, including:

* Colors
* Fonts
* Spacing and sizes
* Borders and radiuses
* Individual components

Update the theme in the Partner Portal and it takes effect immediately for patients using the app.

## Email Theme

App theming only covers the Patient App itself — transactional emails are styled separately, via the **Email Theme** setting. This controls the look of every transactional email MDI sends: intake links, notifications, order updates, and similar system messages. Configuring it means patients see a consistent visual identity whether they're inside the app or reading an email that got them there.

## Recipes

### Fully on-brand Patient App

Set primary/secondary colors and background to match your brand palette, then layer in custom CSS for anything the color tokens don't cover, such as custom fonts, button shapes, or spacing. Because this is runtime-driven, you can iterate on it freely without waiting on a release cycle.

### Branded email end-to-end

Configure the Email Theme so transactional emails visually match your site, then pair it with a Custom Domain for email sending so those emails also come from your own domain rather than MDI's default. Together, this makes an intake or notification email indistinguishable from any other email your brand sends.

{% hint style="warning" %}
Theme changes apply immediately to the live Patient App and outgoing emails. Preview changes in a sandbox environment before rolling them out if you're making a significant visual change close to a launch date.
{% endhint %}

<details>

<summary>What Isn't White-Labeled</summary>

Most of the patient experience — including most email and SMS notifications — carries your branding once Theme Settings and Email Theme are configured. A handful of security- and compliance-critical notifications are the exception: 2FA codes, data access/deletion confirmations, and email-update confirmations always show MDI's own name, regardless of your theme settings. This is by design — patients need to trust that a verification code or a data-rights confirmation is genuinely coming from MDI. See \[Controlling Patient Notifications]\(/pages/orNWq753fSsLvgXOVCmD) for the full notification catalog and which types are white-labeled.

</details>


---

# 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/exploring-features/theme-settings.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.