> For the complete documentation index, see [llms.txt](https://docs.high-mobility.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.high-mobility.com/oem-guides/ford/onboarding.md).

# Onboarding

## In-fleeting Requirements

### Consent on Ford Pro

For Ford, the Fleet Manager must grant consent to **High Mobility GmbH** as a data provider in their Ford Pro account. Consent can be granted for the entire fleet, for a selection of VINs, or for individual VINs that can be uploaded to Ford Pro.

The Fleet Manager can also enable **Auto-Consent** for **High Mobility GmbH**. Once enabled, any Ford vehicles added to the Ford Pro account are automatically consented, so no additional steps are required for newly added vehicles.

This is a one-time consent and asynchronous process. Once consent has been granted, you can activate vehicles at any time using our [**Fleet Clearance API**](https://docs.high-mobility.com/docs/getting-started/fleet-clearance).

You can share the following public **Ford Pro instruction link** with the Fleet Manager or Fleet Owner:

{% file src="/files/Ko4WfvQG4Zj8lx1BIpdo" %}

### Ford Pro access

* **If there is no existing account**, the Fleet owner can sign-up and setup an account using this link <https://fleetaccount.ford.com/third-party-signup>

**Available markets:** Austria, Belgium, Canada, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Luxembourg, The Netherlands, Norway, Poland, Portugal, Romania, Spain, Switzerland, United Kingdom, United States.

{% hint style="danger" %}
**Please contact High Mobility Support through** [**support@high-mobility.com**](mailto:support@high-mobility.com)**, if:**

* your market is not listed on the Ford Pro sign-up page
* there is an existing Ford Pro account without the “Service Provider” tab
  {% endhint %}

## Privacy settings

Some Ford vehicles may have the in-vehicle settings Customer Connectivity Settings (CCS) switched off, which prevent the vehicle activation to succeed and data transmission.

Ford has provided the following public guide to instruct where to switch on the settings in the vehicle:

{% file src="/files/U2jEC673fA1oICRX5Jlt" %}
Ford Pro Software – In-Vehicle Connectivity Settings Instructions
{% endfile %}

{% file src="/files/VHeUeD8VwPwkEBxYCFew" %}
Ford CCS Settings Manual
{% endfile %}

To enable the CCS settings, Ford recommends that the driver switch on the ignition within the next 24–48 hours.

## OEM Workflows

### Ford Activation - <mark style="color:cyan;">Happy flow</mark>

<figure><img src="/files/jq9KaIi1ZPH6qmxgd7OK" alt=""><figcaption></figcaption></figure>

### Ford activation - <mark style="color:red;">Unenrollment in progress</mark>

### Ford Activation - <mark style="color:$warning;">No Consent on Ford Pro</mark>

<figure><img src="/files/TINFFrMs0SjjruCXFlaC" alt=""><figcaption></figcaption></figure>

If the the Consent is not yet granted on Ford Pro we do keep the vehicle as  `pending`  for 10 days.&#x20;

Our system will check if there is a consent **every 12h** and retry the activation periodically. This can be considered as an asynchronous process and gives you room to still grant consent even if you have created a clearance for your vehicles.

After **10 days** the activation will time out and the clearance will be set as  `rejected` .

When the Ford consent is not yet granted, you can detect it in the `reason` field of the GET endpoint the clearance response  `consent assignment missing`:

```json
curl -X GET https://api.high-mobility.com/v1/fleets/vehicles/WF0XXXXXXXXXXXXXX
{
  "status": "pending",
    "brand": "ford",
    "vin": "WF0XXXXXXXXXXXXXX",
    "tags": {},
    "changelog": [
        {
            "reason": "consent assignment missing",
            "status": "pending",
            "timestamp": "2026-08-05T09:37:14"
     }
    ]
}
```

### Ford Activation - <mark style="color:$warning;">In-vehicle Connectivity Settings not switched on</mark>

<figure><img src="/files/2tc0qy8xQaTWKlE7wddI" alt=""><figcaption></figcaption></figure>

\*Please verify the in-vehicle Connectivity Settings following the followings Ford instructions. <https://drive.google.com/file/d/1S_4l9JvRJU8E4oAk50LkWMsphxlC4-df/view?usp=sharing>

{% hint style="info" %}
For any support related issue please contact <mark style="color:cyan;">**<support@high-mobility.com>**</mark>
{% endhint %}


---

# 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.high-mobility.com/oem-guides/ford/onboarding.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.