> ## 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 DNSFilter and map organizations

> Choose DNSFilter data and link organizations to portal companies

<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 DNSFilter to review mapped organizations, sites, filtering policies, roaming clients, and traffic or blocked threats.

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

In DNSFilter, open **Account Settings > Security > API Keys** and create a key for a dedicated user with the required read access. Copy the key immediately; it is shown only once.

## Set up the connection

1. In **Connect**, enter the API key.
2. Select **Test connection**, then **Save and continue**. For an existing connection, test changed credentials and select **Save changes**.
3. Open **Choose data** and review **Sync roaming clients** and **Sync blocked threats**. Each switch saves immediately. Roaming clients can link to devices by hostname; blocked threats come from query-log records for the last seven days.
4. In **Import or match companies**, link DNSFilter organizations to portal companies. Those mappings determine where sites, clients, policies, and traffic belong.
5. Continue to **Review** and inspect the available data before completing setup.

Keep the masked key to retain stored credentials. Dataset switches in **Choose data** save immediately and are separate from credential changes.

## Troubleshooting

* **No organizations or data:** confirm API read access and wait for organization discovery.
* **A company has no data:** check its organization mapping before changing filters.
* **No roaming clients or blocked threats:** confirm the relevant sync option is enabled and saved. No blocked events in the seven-day window does not prove the integration failed.
* **Wrong devices linked:** inspect hostnames and the organization-to-company mapping before importing or remapping records.

## 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.