I have a user with WPC that not everyone has badges. Some have badges, some use Castle from their phones to access doors and computers (is this an option) and others will need to use pin numbers to login. What is the best method to add the PIN numbers to the user accounts. Other than LDAP mappings, I do not see a method to add pin numbers to the user accounts. Thanks
PIN numbers can be added manually by the administrator (one at a time), via LDAP import and via CSV import.
Choose an attribute in Active Directory (assuming you are using this with LDAP) on your user accounts, for example employeeID. Then, within the Advanced LDAP configuration for your domain in Workplace Cloud, map the pin number attribute in workplace cloud to the active directory attribute employeeID. Fill the user's pin number into the employeeID attribute. When the user auths later, workplace cloud will pull in this pin number attribute that you have mapped in your Advanced LDAP configuration.
To register employees, download the workplace cloud client and install on their machine(s). Have them sign in through workplace cloud by right-clicking the icon in the system tray and choosing "sign in". You need to also be sure you have auto-registration turned on within your workplace cloud configuration for authentication settings. The user will be asked for thier email address. When workplace cloud recognizes the domain of the email address and that it is part of your workplace cloud tenant, it will then present the user with the domain\username login and password prompt, which will authenticate to your Active Directory over LDAP. Assuming this is sucessful, the user will then be added beneath the "users" tab and will now be able to sign in at the printer by keying in their pin (employeeID attribute within AD).
Hope this helps you out.
On the Users tab, if you select Import Users from File via the Action menu, there is a download template option.
Regarding the question about manually adding the user. I assume this customer is configured for LDAP authentication and the user was trying to log in via Alternate Login at the printer: Email, Domain\Username and Password. You can on-board a new user with this method only if the email domain of the user has been mapped to the company code (backend mapping). This allows the solution to skip the normal email verification step for new LDAP users. If the mapping is not in place, the user will be rejected (access denied).