Manually creating users
Apart from importing users or setting up automated user provisioning (more on that below), users can also be manually created. Unlike other objects such as Assets, Requests, or Contacts, users (referred to as System Users) aren't created independently. Instead, they are always created based on existing contacts, which can be persons or organizations.
...
Please note that you will only see these options if you have administrator or user manager access rights.
Basic user settings
When enabling access on a contact, the automatically created system user is shown:
...
For more information on the other user settings, see: Personal settings
Emailing Login Credentials
...
Once the system user has been set up correctly, login credentials can be sent. These credentials include:
...
Direct Email to User: Send the login credentials directly to the email address of the contact linked to the user. To do this, use the "Change Username/Password" button on the user page and select "Email new password to user" on the next screen.
Email to yourself: Send the login credentials to the email address linked to your own user. This option is relevant if you need to change the password (as it requires the automatically generated password). To do this, use the "Change Username/Password" button on the user page and select "Email new password to myself" on the next screen.
Scheduled Email: Schedule the sending of login credentials for one or multiple users at a specific moment in time. For example, if the customer will go live on a specific future date, you may want the login credentials to be sent on that date. To use this feature, go to the users overview via the "Users" button on the administrator startboard. Search for the relevant users and select them from the list. Then, use the "Set password send date for selected users" option.
...
Single Sign-On
If the customer is using Single Sign-On (SSO), there's no need to send login credentials to the user, as they will use their own identity provider to log in (e.g., Office 365). In this case, different settings apply. Refer to the SSO configuration for WPM for more information.
...
Just like the other data import sheets, it is also possible to import users based on an excel template. For more information about the default data imports, see: Imports
Standard Employee Interfaces
...
When a large customer requires access to Workplace Management for all or most of its employees, managing user accounts manually becomes cumbersome due to the frequent changes in personnel. To streamline this process, a Standard Employee Interface can be established.
This interface connects Workplace Management with the customer's employee management application, such as Okta or Azure. By integrating with this application, user accounts can be automatically created and archived based on data from the active directory. For detailed instructions on setting up this integration, refer to the documentation on Standard Employee Interfaces here: Standard Employee interfaces
Custom Employee Interfaces
...
Alternatively, a more customized approach can be implemented using an SFTP (Secure File Transfer Protocol) interface. This involves automatically importing files from an FTP server to manage employee data. For more information on setting up a Custom Employee Interface, refer to the documentation available SFTP import/export setup
Via Workplace Experience
If the customer is also using Workplace Experience, it is possible to automatically create a contact and related system user based on a login into the workplace app. For more information about this, see; [To be added]
For further details on this integration and user creation within Workplace Experience, refer to the comprehensive guide available in the general article about user creation in Workplace Experience: Users & Groups