> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/set-up-driver-identification.md).

# Set up driver identification

## Question

How to use and set up driver identification?

## Answer

The first step in setting up the driver identification system is to configure the tracker so that it sends RFID/iButton/BLE identification data. Different manufacturers provide different tools for configuring identification. Contact your tracker manufacturer to enable sending identification data to the platform. Once configured, you should be able to see the identification data in Air Console as soon as it is triggered by an RFID card or other identification medium.

Once the tracker is configured, you can proceed with setting up the platform. The main task is to populate the list of drivers in the Field Service section and specify the hardware keys in the drivers' records:

![](/files/ed7a8a2e34fbae1931581802d6ce97c1f96c582c)

A hardware key is usually a HEX code text string. Enter a hardware key for each driver in the list.

You can also use import to bulk import drivers with predefined hardware keys and other properties.

Once the driver list is ready, driver identification starts working automatically. Upon authorization on the tracker side, the tracker sends a hardware key to the platform, and the platform recognizes it and assigns a certain driver from the list to the tracker. Now you should be able to build reports and track the driver assignment status in the Tracking module (tracker widgets).

## Links

* [Drivers](/docs/user/guide/fleet-management/drivers.md)


---

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

```
GET https://navixy.com/docs/qna/using-navixy/set-up-driver-identification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.