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

# Provider Access Control

> Control which telematics providers fleets can connect through the Consent Flow.

Provider data coverage varies. Use Provider Access Control to prevent fleets from connecting providers that do not meet your data requirements.

Before changing provider access, review the [Provider Explorer](/providers/explorer) to compare support for vehicles, locations, HOS logs, IFTA data, and other models.

## Provider access modes

Terminal supports three provider access modes:

* **Allow All Providers**: Fleets can connect any provider available through Terminal.
* **Allow Only Selected**: Fleets can connect only the providers you select.
* **Block Selected**: Fleets can connect any available provider except the providers you select.

Use **Allow Only Selected** when you maintain a strict list of approved providers. New Terminal providers are not automatically added to this list.

Use **Block Selected** when most providers meet your requirements and you only need to exclude specific providers. New Terminal providers remain available unless you block them.

<Note>
  Provider Access Control determines whether a provider can be connected. It
  does not change the data models or attributes that the provider supports.
</Note>

## Configure provider access

1. Log in to the [Terminal Dashboard](https://dashboard.withterminal.com/).
2. Go to **Settings > Provider Configuration**.
3. Find the **Provider Access Control** section.
4. Under **Provider Access Mode**, select **Allow All Providers**, **Allow Only Selected**, or **Block Selected**.
5. If you selected **Allow Only Selected** or **Block Selected**, choose the providers to include in the list.
6. Click **Save Changes**.

## What fleets see

Allowed providers appear as available options in the Consent Flow.

At the bottom of the provider list, fleets can select **Request Provider** to search providers that are not currently available for connection. Fleets normally use this option to request support for a provider that Terminal knows about but does not yet support.

Blocked providers are removed from the main list and appear under **Request Provider** instead. If a fleet selects a blocked provider there, Terminal displays an **Integration Not Supported** message explaining that the provider does not meet your data requirements. The same message appears if the fleet opens the Consent Flow with that blocked provider already selected.

<Accordion title="Customize the blocked-provider experience">
  You can also direct fleets to your own help page by setting a **Blocked
  Provider Redirect URL** in a [Consent Template](/guides/consent-templates). In
  that case, Terminal does not redirect the fleet automatically. The
  blocked-provider message includes a **Continue** button that opens the
  configured URL in a new tab. Use the destination page to explain your
  requirements, recommend another provider, or provide contact information for
  support.
</Accordion>

## Review your configuration

Provider coverage changes as Terminal adds integrations and expands existing ones. Review the Provider Explorer and your provider access configuration periodically so fleets can connect every provider that meets your requirements.

## Related docs

* [Provider Explorer](/providers/explorer)
* [Link Component](/link-component)
* [Consent Templates](/guides/consent-templates)