In the user management, all users are managed in the respective car manager abbreviation / location. Users can be created independently as part of the car manager package used, and the maintenance and deletion of users is also carried out independently.
Users have access to this area in order to make changes to their contact details or, for example, to enter absences. Access to critical settings (such as assignment of requests/superior settings, etc. is controlled by rights and is usually managed by supervisors.
Note:
One location is visible with all the details, others can be used with the symbol

be opened. In addition, the number of free users in the respective location is mentioned.
Overview
In the overview of the user management, all users are mentioned with username, first and last name, rights group (n) and the time of last login.
Users can be created, edited or deleted.
Note:
- With activatedGroupAppAll linked locations and all users are shown here.
- Users without the right to edit other users do not reach this area, but directly to the processing of their own user data.
- When the user quota is exhausted, no new user can be created. Via the upgrade link, with appropriate rights directly to theOrder routejump off - here the next higher user package is preselected.
User system
When a user is created, core data of the new user is entered. The following fields should be filled in:
- Username (free selectable if not yet assigned)
- Email address
- Name
- First name
- Superiors
- Rights group
Upon storage, the new user automatically receives an e-mail with initial access information, which enables logging in after setting a password. The data should then be completed on the user side.
User data part 1
In the first part of the user data, the personal data of the user is stored.
Notes:
- The username is used for login and can only be used once in the system.
- An e-mail address can be stored with several users.
- The contact details should be kept up to date independently by each user, as they may. in external communication byLMS template/ Autoresponders or printed matter are used.
User data part 2
In the second part of the user data, data is defined that are also used in external communication or that is relevant for escalations and rights of use.
Notes:
- With theTwo-factor authenticationthe user receives a code by e-mail when logging into the car manager. This must be entered so that the user has access.
- The supervisor is involved in the escalation chain of leads by depositing with the user. The registered supervisor has access to the leads of the user and receives if theSet timesa notification.
Email signature
In the e-mail signature, the user can store his own signature, which is applied to all communication from the car manager LMS. A vCard can also be activated.
Note:
- If a vCard has been activated, it will beEmail communicationSent in the Leads section.
- It is not necessary that legal information about the company is ready inLMS templateDeposited here are to be re-entered.
Personal program settings - vehicle list
In the personal program settings - vehicle users can define which financing / lease should be displayed and which content should be shown in the info icon in the vehicle list:
Personal program settings - vehicle detail page
With this setting, the publishing status of images can be made visible in the detail view.
Personal program settings - advanced search
These settings can be used to define which vehicles should be set automatically during the extended search or whether a stored search should be stored as the default display.
Absence list
In the absence list, a user can define absences or view registered absences of the past two years. Within entered absence periods, the user does not receive new leads.
Notes:
- It is not necessary toGeneral closing daysRegister here as well.
- Assigned leads and responses to existing leads remain with the user even in the absence of registered absence.
- Escalations also continue during absences. It is therefore strongly recommended to deposit deputies.
- If an absence is entered, but the corresponding user is the last remaining user (or the defined fallback user), a warning message comes:

LMS requests
In the LMS Requests section, it is defined whether a user should automatically receive new requests or whether only one assignment is possible.
Note:
- Please note the settings / instructions for the LMS configuration and theLMS basic settings. .
LMS distribution groups
LMS Deputy
Registered LMS deputies have access to the leads of the respective user - regardless of supervisor settings or other rights.
Notes:
- Deputies have access - as long as they are entered here - access rights, even in the presence of the user.
- A deputy does not receive the rights of the represented person
- The distribution of requests is also not redirected to the deputy
- Several deputies are possible.
Users to notify
Users can be defined who should receive a notification of new requests for the user.
Notes:
- It is advisable to set this option only in the absence, otherwise the entered users will receive information about operations where they do not need to operate.
- In the absence, simultaneous registration of representatives and user to be notified is recommended.
LMS email notifications
Users can define for themselves what kind of processes they would like to be informed about by e-mail or browser notification.
Note:
- When notifications are switched off, a user must proactively monitor the area of the LMS or the status of his requests / escalations in order to be able to react.