!--a11y-->
Administrative Functions 
The application supports one driver language (used on screens) and up to two customer languages (used for output). You make the appropriate language settings in the backend Implementation Guide. The driver language is explicitly set. You can specify the customer language in the DSD Connector Cockpit andconfigure which two output text languages are to be transmitted to a device.
All transactions and screens can be assigned to authorization roles. If a transaction or a screen is not assigned to a role, no authorization check is performed. Some of the mobile transactions are meant to be used by someone other than the driver.

It is possible that check-in and check-out discrepancies require a supervisor’s approval. In this case, you would assign discrepancy approval to a supervisor authorization role. This means that sales representatives would have to give their devices to a supervisor who would enter his password and perform the transaction. The supervisor’s authorization expires on the device after he has carried out the transaction.
You can assign a role to a group of mobile devices and define a password for this combination. This password is then used on all mobile device that belong to this group.
System dates and time stamps are automatically recorded for each visit, activity, and document. This leaves an accurate audit trail of what was performed when and how long each task took.
