> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/settings/managing-integration-categories-and-regional-settings.md).

# Managing Integration Categories and Regional Settings

Harmony gives you fine-grained control over how integrations are organized and how device data is collected across your organization. This article covers two areas of the Settings experience: the dedicated **SaaS Procurement** section that groups your procurement integrations together, and the regional configuration options available when connecting Mobile Device Management (MDM) sources.

***

### SaaS Procurement Integrations

Procurement tools are now grouped in their own **SaaS Procurement** section under **Settings > Integrations**, separate from the rest of your SaaS catalog. This makes it easier to find, connect, and manage your procurement sources without scrolling through unrelated integrations.

The following tools appear in this section:

* **ZipHQ**
* **NetSuite**
* **Mesh Payments**

#### Connecting ZipHQ and NetSuite Together

ZipHQ and NetSuite both track overlapping contract and spend data. If you connect one of these tools and then attempt to connect the other, Harmony will display a warning to let you know that a procurement source is already active.

You have two options when you see this warning:

* **Connect both sources** - You can proceed with connecting the second tool and manage any duplicate contract or spend records manually.
* **Wait for automatic deduplication** - If automatic source deduplication is available for your plan, you may prefer to hold off until that feature handles overlapping records for you.

Harmony does not block you from connecting both tools at the same time. The warning is informational, giving you the context you need to make the right decision for your organization before proceeding.

#### Mesh Payments

Mesh Payments can be connected independently without any overlap warnings, since it tracks different spend data from ZipHQ and NetSuite.

***

### Regional MDM Support

When connecting an MDM integration, Harmony now supports regional configuration to ensure device data is collected from the correct instance of your MDM platform.

#### Why Region Matters

Many MDM providers host data in region-specific environments - for example, separate instances for the United States and the European Union. If you select the wrong region during setup, Harmony may be unable to reach your MDM instance or may retrieve incomplete device data.

#### Configuring Your MDM Region

When you add or edit an MDM integration under **Settings > Integrations**, you will see a region selector as part of the connection flow. Select the region that matches where your MDM tenant or instance is hosted.

If you are unsure which region applies to your organization, check your MDM provider's documentation or contact your MDM administrator before completing the connection.

***

### Related Settings

* To manage all integrations in one place, navigate to **Settings > Integrations**.
* To review connected procurement sources and check for duplicate records, open the **SaaS Procurement** section within the Integrations page.
* For MDM connections, review the region selection any time you edit an existing integration to confirm it still matches your provider's hosting configuration.


---

# 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.harmony.io/settings/managing-integration-categories-and-regional-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.
