User Management
Adding a User
11 min
important prerequisites to adding a user the user's organizational structure must already exist in the system for more information, please see organizational structure docid\ fnzhj8 4t7 brpyyswkzt the user's supervisor must already be a user in the system and must be the supervisor of the team to which you wish to add the user to add a user in user onboarding, click on the "add new user onboarding record" button when you click on "add new user onboarding record", you will see step 1 of the user onboarding flow personal info step 1 of user onboarding is entering the user's personal information lan id this represents the user's identification in the system and is often the same as "agent id" this needs to be unique across the system first name and last name displayed throughout the system agent id select the toggle on the right end of this field to make it the same as the lan id pbx id this can be a unique number/extension or simply the same as the lan id note there is a system setting which allows entry of non numbers in pbx id if you want to be able to allow entry of letters in pbx id and your system is not allowing that, let your it support know org unit identify the level/team with which this user is associated see image below for an example note an agent (a user with profile = agent) can only be a member of a team a team is the lowest level of the hierarchy ("east team a" in the image above) a supervisor (a user with profile = supervisor) can be a member of any level of the hierarchy profile select either "agent" or "supervisor" please see note directly above supervisor click the drop down and select the agent's supervisor from the list if the supervisor's name doesn't appear, then that supervisor is not associated with that team yet important notes re supervisors a supervisor has access to all agents of all teams within the hierarchy to which they are assigned example if department "support" has 2 teams within it, "team a" and "team b", then assigning a supervisor to the department support will provide that supervisor with access to all agents assigned to team a and team b more than 1 supervisor can be assigned to the same specific group in hierarchy for example, the support department could have multiple supervisors assigned to it (e g , so that the supervisors can back each other up when managing their respective teams) all users require that 1 supervisor be assigned except those at the country (highest) level where the supervisor = "na" (not applicable) once you have completed all of the above fields, click "next" profile picture in step 2, you specify the image which will be used to authenticate an agent's face once you have selected a facial image, size the bounding box shown to include below the chin and the top of the head select the green check button important the quality of face authentication is related to the quality of the profile picture supplied please refer to profile pictures docid 1m6ndwlmllbeetk7rscl1 in the agent help for more details features (agent specific) the feature selections on step 3 of user onboarding are agent specific in most cases, you are safe making no changes here and simply clicking on "next" note there are a few situations where features are assigned to users, but in general it is best practice to assign features at the team or higher level for more information, please see feature templates docid hqo csge95ubkuylvrh1 role mapping the last step of user onboarding is assigning 1 or more roles to the user in most cases, you will specify a role such as "agent" to agents and "supervisor" to supervisors you can leave access role, crm name, and text template blank speak to your system administrators for more guidance on what role(s) to use roles are related to the following remote security rules docid\ mxqk0wmz iye61wlioe2h these define what should happen when a given security event occurs in the secure work from home application on the agent's desktop what administrative and/or reporting access a user with this role should have please see roles docid\ fsya bvujbjw2wgch3erv for more information click "save" to create the user modifying a user to modify an existing user's configuration, go back into user onboarding and locate the user you can use the search box in the upper right to search by first or last name or lan/agent id then click the pencil button for the desired user in the results displayed see below when you make a change to a user, you must specify a reason for modification this is done in the modify reason field which appears on all admin pages in ocm and is required in order to save any changes this is to communicate to auditors after the fact why a change was made