> ## Documentation Index
> Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect ThreatMate and map customers

> Map ThreatMate customers and review assets and security findings

<Note>Branch preview: these instructions describe the current setup flow. Provider availability depends on the integrations enabled for your portal. Production verification is pending.</Note>

Connect ThreatMate, link its customers to portal companies, and review the assets and security findings available for those mappings.

Open **Settings > Integrations**, find the provider in the directory, and open its setup. You need an MSP staff account with permission to manage integrations. Company users should ask their MSP to connect the service.

## Before you start

Use a ThreatMate API key with read access to customers, segments, assets, and alerts. Paste the key without a `Bearer` prefix. The supported **ThreatMate API URL** is `https://app.threatmate.com`.

## Connect and map customers

1. In **Connect**, enter **ThreatMate API URL** and **API key**.
2. Select **Test Connection**, then **Create Integration** after verification. Existing connections use **Save connection**.
3. Continue to the customer-mapping step and allow the initial discovery to finish.
4. Link each ThreatMate customer to the corresponding MSPortal company. Assets and findings sync only for mapped customers.
5. Open the review step and inspect mapped customers, assets, and security findings. Map at least one customer and start a sync before finishing setup; the sync continues in the background.

Connection and mapping totals cover the integration across companies. Verify the correct customer mapping before expecting a company's assets or findings to appear.

## Troubleshooting

* **API URL rejected:** use the supported official ThreatMate host.
* **Test rejected:** check the key's read access and remove any `Bearer` prefix.
* **No customers yet:** allow initial discovery to finish; large accounts can take a few minutes.
* **No assets or findings:** confirm the customer is mapped and another sync has run.
* **Sync failed:** correct the connection or permission problem and retry; previously collected data is retained.

## Related guides

* [Integration setup guides](/user-guides/integrations/index)
* [Map and import companies](/user-guides/integrations/import-companies)
* [Integration troubleshooting](/user-guides/integrations/faq)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.