Configuration Import users into the system via CSV import or Active Directory import, or create them manuallyEach user can serve as a template for the user settings. If sufficient user licenses are available, it is a good idea to create your own template user, since its settings are not accidentally changed during operation. Define target user groupThe users for whom the settings are to be transferred must be members of a user group. The user group is only used for logical grouping during the copying process of the settings and can be deleted again after the process has been completed. Configuring the User Template PRO ModuleCreate a module instance and name it with a name of your choice, e.g. "UserTemplate". In the User Template Application tab, select the target user group whose users you want to apply the settings to. Select a template user. The selected user settings of this user are applied to all members of the target user group. In the tab "Mass changes" you have the possibility to set the displayed phone number of the target users to their primary external phone number. Otherwise, the phone number is not displayed by default. You can also reset the passwords of all users. The User Template PRO module changes the Configuration or the Features & Benefits of users within the target user group. When copying function keys, however, no autoprovisioning process is triggered on the terminal device. To transfer the function keys to a terminal device, please use the function "Transfer keys to ..." within the function key configuration of a user. Alternatively, you can log on to hotdeskable mobile devices again to trigger provisioning or reset the mobile device to factory settings. This behavior is intended and will not be changed, since depending on the terminal device it is not possible to reliably assign the function keys (e.g. if a call is active on the terminal device), manually configured keys on the terminal device are not overwritten in this way and, depending on the terminal device, a restart would otherwise be triggered with loss of the network connection. |
Care must be taken when copying user rights ! If, for example, a user with admin rights serves as a template, all users in the target user group also receive admin rights! Conversely, all users in the target user group are deprived of admin rights if the template user does not have admin rights. This way it is possible to withdraw admin rights from all users. Administration of the system is then no longer possible. Admin permissions for a user can only be restored by manually intervening in the STARFACE database. |
ConstraintsBasically applies: You can copy and use all function keys that do not depend on properties of the user itself, since these properties may not be available or identical for the target user. If you create and copy a function key in the template user that does not make sense in the target context, a function key is created for the target user, but it is marked as "incorrect". Function keys that cannot be successfully copied are, for example: - Log on/off group
- Activate/deactivate call forwarding
- Call number signalling
Copyable without restriction are e.g. BLF and direct dialling keys, idle, park & orbit, DTMF and empty key. The function of these keys is independent of the user. If, for example, a function key "Activate/deactivate call forwarding" is created for a template user, this refers to the phone numbers of the template user. These phone numbers may not even exist for the target user, which is why the function key would not make sense for the target user. The same applies to signaling phone numbers and - although less obvious - logging/unlogging for groups. The User Template PRO module abstracts the concrete function key type. That is: The module can also copy function keys from future versions. Whether they also work for a target user depends on the concrete function of a function key. |