Creating a Driver

In the corresponding monitoring panel choose the appropriate mode (Drivers), click the New button, and indicate required parameters.

Name
Give driver a name that will be visible during the tracking process and in reports.

Code
Enter unique driver code needed to identify the driver if an automatic method of binding will be used. Codes of different drivers should be different.

Description
Type any comments (optional). It is shown in driver's tooltip.

Phone number
Enter driver's phone number. It will be shown in driver's tooltip and can be used to send SMS messages to the driver and make calls. Note that units or drivers with the same phone numbers cannot exist in the system. If you attempt to create a driver with a phone number that is already reserved to another driver or unit, a special alert will be displayed, and this phone number will not be saved.

Mobile key
Password for mobile authorization.

Exclusive
If this flag is enabled, this driver can be the only one assigned to a unit. In case you bind this driver to a unit (in real time) which already has one or more assigned drivers, those drivers are reset automatically. This flag works only for drivers within a common resource.

Photo
To quickly identify a driver, you can attach their photo or any other image. To do this, press the Browse button and find and load an image from the disk. Supported formats are PNG, JPG, GIF, and SVG. In the driver's editing dialog you can delete an image used. To do so, point a cursor on it, and click the appeared delete button. Click OK to save changes, or Cancel to dismiss them.

Custom fields
Create driver's card adding any information as custom fields (information may include external links). They are shown in driver's tooltip and can be summoned in reports. Note that custom fields with the same name cannot coexist within one particular driver.

At the end click OK. The new driver appears in the list.

:!: Like any other resource contents, drivers can be imported and exported through files or directly from one resource to another. However, that is not true for driver groups.

Was this helpful?
Thank you!