> 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/volkswagen-group/onboarding.md). # Onboarding ## In-fleeting Requirements For the VW brands, a document needs to be signed by the Fleet owner/operator, which will apply to the entire Fleet. This step is mandatory for all third parties/solution providers as it’s a legal requirement. The HM Biz Dev Team will provide you with a custom Boldsign link that you can provide to your Fleet customers in order to digitally collect thee signature. This will be considered as a one-time consent on their whole Fleet of VW Group vehicles (including the brands Audi, Skoda, Volkswagen, SEAT, Cupra) ## Privacy settings For Audi, Skoda, Volkswagen, SEAT and Cupra, vehicles could have the Privacy settings switched on. This setting will need to be changed in the vehicle, and you can also take the opportunity to check if the latest Software updates need to be installed in the vehicle. * Note: Once the vehicle is successfully activated, the Driver can no longer change the Privacy settings in the vehicle. This ensures data transmission while the vehicle is connected. \ You can provide the following instructions to your Fleet customers or Fleet operators in order for the Privacy settings to be changed in anticipation of the onboarding and activation of the vehicles. **Links to Instructions for manual deactivation of Privacy Mode:** ℹ️ [Volkswagen Privacy Setting EN](https://drive.google.com/file/d/1ZM7AMq_6Ws8TjJyuW_GskBZ2p0ejbC6q/view?usp=sharing) ℹ️ [Audi Privacy Setting](https://drive.google.com/file/d/1bzwhD7S6_qAKkk0LtEvuq-WY4PMNDmO-/view?usp=sharing)[VW\_Privacy\_Setting\_EN.pdf](https://drive.google.com/file/d/1ZM7AMq_6Ws8TjJyuW_GskBZ2p0ejbC6q/view?usp=sharing)[ EN](https://drive.google.com/file/d/1bzwhD7S6_qAKkk0LtEvuq-WY4PMNDmO-/view?usp=sharing) ℹ️ [Skoda Privacy Setting EN](https://drive.google.com/file/d/1ivEflkt3vEkRB-z7y7dhCNrVvMIX5zps/view?usp=sharing) ℹ️ [Seat & Cupra Privacy Setting EN](https://drive.google.com/file/d/15SOc2I0qhSwTkp5PMD4qoqAzSsP-aL5z/view?usp=sharing) ℹ️ [Volkswagen Commercial Vehicles Privacy Setting EN](https://drive.google.com/file/d/1C-GKW1X9L4T2af3HgzaLoBA55Za9uNrO/view?usp=sharing) {% hint style="warning" %} \*MOD4 vehicles and Audi vehicles are not able to provide live location data {% endhint %} ### Fleet Clearance In order to onboard VW Group vehicles, you will need to additionally specify the name of the Fleet customer as a "tag" `vw-group-customer-name` in our [Fleet Clearance API](broken://pages/ayVEW04npPdvZt6ZkHpf). Please consult our documentation: ℹ️ [Fleet clearance tutorial - Using tags](https://docs.high-mobility.com/guides/cloud/service-account-api-fleet-clearance-tutorial/#using-tags) This tag should correspond to the Fleet operator business name, which we associate with the specific VIN activation. The following shows an example of how vehicle clearance objects are passed in with a tag set: ```json curl -X POST https://api.high-mobility.com/v1/fleets/vehicles \ --data ' { "vehicles": [ { "vin": "VIN01234567890123", "brand": "audi", "tags": { "vw-group-customer-name": "Car Operations Ltd." } } ] }' ``` {% hint style="info" %} If you are a direct Fleet Operator or always activate VINs for the same Fleet Operator, our support team can configure a default Business name for a specific data project. This removes the need to include the `vw-group-customer-name` tag in the Fleet Clearance API. Please let us know during onboarding or contact our support team at ****. {% endhint %} ### OEM Workflows #### Privacy settings during a clearance If the privacy settings of a VW Group vehicle are enabled during the activation attempt, the vehicle will stay in the `pending` state while we keep retrying the activation. If the settings have not been disabled within 5 days, the activation attempt is rejected. When privacy settings are blocking the activation, you can detect it in the `reason` field of the clearance object: ```json { "vin": "VIN0TESTVIN000000", "status": "pending", "brand": "volkswagen", "changelog": [ { "timestamp": "2025-01-22T10:42:14", "status": "pending", "reason": "privacy mode is enabled" } ] } ``` #### EV vehicles with an active primary user Currently, the VW API does not allow vehicles that are activated via their B2C app to be enrolled into a fleet. If this occurs, the vehicle will be rejected with the following reason: ```json { "vin": "VIN0TESTVIN000000", "status": "rejected", "brand": "volkswagen", "changelog": [ { "timestamp": "2025-01-22T10:42:14", "status": "rejected", "reason": "primary user enrolled" } ] } ``` To resolve this issue, please perform the factory reset using the infotainment system: (Go to Home > Vehicle Settings/Setup > Reset to default settings.) {% hint style="info" %} This limitation is expected to be resolved in Q1 2026. {% endhint %} #### Vehicle with no data If you attempt to activate a vehicle and the vehicle doesn't transmit data, the vehicle stays in `pending` state. In the API you see with this status ```json { "vin": "VIN0TESTVIN000000", "status": "pending", "brand": "audi", "changelog": [ { "timestamp": "2025-01-22T10:42:14", "status": "pending", "reason": "no data received" } ] } ``` If after 10 days there is no data transmitted, the vehicle gets rejected: ```json { "vin": "VIN0TESTVIN000000", "status": "pending", "brand": "audi", "changelog": [ { "timestamp": "2025-01-22T10:42:14", "status": "pending", "reason": "no data received" }, { "timestamp": "2025-02-12T10:42:14", "status": "rejected", "reason": "activation timeout: no data" } ] } ``` ### More Information If you have any questions, please contact us on [Slack](https://slack.high-mobility.com/) or [send us an email](mailto:sales@high-mobility.com). --- # 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/volkswagen-group/onboarding.md?ask=&goal= ``` `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.