Importing users

This page provides an integrated view of all user records found on all connected components (Users and Services Application, MBGs, MiCollab Client Service).

All records can be imported to Users > Manage with the options located at the bottom of the table (available if users have been selected):

Select the Deployment Profile you would like to use.
Select the header row check box to select all records across all pages, or select the check boxes to the left of every row to select individual records.
Select Import. If you would like to deploy to users immediately, click Import and Deploy.

When MiCollab Client is configured as a stand-alone deployment without MiCollab or an MBG, you must enter the PBX SIP fields manually. See Manually Create Users for more information.

Once the records have been imported, they will appear in the Manage view.

Note:

Imported records cannot be modified.

Setting	Description
Firstname	These pieces of information are most often imported from other applications (such as MBGs), or entered manually. Go to Configuration > Connections to MBGs to set up these connections. Go to Users > Import Users to import user account information from the set-up connections.
Lastname
Directory Number
PBX Number	PBX number or name.
MBG UserName	The user name as it is synced from the MBG or entered manually.
MiCollab Client Service Account	MiCollab Client Service Account that is associated with the user.
E-mail address	The email address that will be used to send download links and authentication credentials to a user.

Note:

To configure the e-mail subject and body, go to Mobile Client deployment e-mail. To use a centralized Deployment e-mail address, edit the deployment profile(s) by clicking Deployment Profiles > Modify.

Note:

The link or QR-Code will be cached by the Redirect Server. However, even if the default e-mail content residing on the Redirect Server is used, for security reasons, user data such as First name, Last name, Directory number, and e-mail address will never be cached.

Note:

irectory extension number with # cannot be synced with the DeployU if a remote MBG connection is used. Replace # with * or use a local MBG connection and Clustered MBGs for synchronizing the data set with their source data set. For example, use 1*001 in place of 1#001.