Manage Data Access
Views allow you to control access to interaction The full conversation with an agent through a channel. For example, an interaction can be a voice call, email, chat, or social media conversation. and employee data. Employee data includes user information. Interaction data includes:
- Call recordings.
- Chat transcripts for interactions routed through ACD.
- Data from any digital channels in DFO.
Only employees you assign to a view have access to the data specified in that view. Each view can manage access to one type of data. The default setting allows users to view all the data available. By assigning a view to a user, you are removing their access to all data except what is specified in the view. See Manage Access to ACD Data to manage access to ACD-related data.
Create Evaluation-Based Views
Create evaluation-based views to restrict access to data related to evaluations. For example, this limits access to data from interactions and quality plans.
- Click the app selector
and select Admin.
- Go to Security Settings > Views.
- Click New View.
- Enter a View Name and a Description.
- Select Evaluation as the Type to restrict access to data related to evaluations.
- In the Teams drop-down, select each team whose data you want employees to be able to access when they are assigned to this view.
- Click Create.
Tips for QM Analytics Flows:
-
Using only the evaluations view:
-
Will restrict evaluations
-
Will enable the playback of the associated interactions
-
Will not restrict the interactions the user will see in the Interactions application, but will restrict the "on the fly" quality related actions that could be triggered from the Interactions. An example would be where supervisors can playback all interactions but only take the quality action for the interactions that belong to their teams.
-
-
In addition, if you want your employees to see only their own interactions in their Interaction application use Interaction View.
-
Minimize the maintenance of multiple QPs and let RBAC control and restrict who is doing what with a single or more QPs.
As an example:
-
3 supervisors/evaluators
-
3 teams defined
-
3 views—one per team
-
Associate the relevant view to the relevant supervisor by the relevant team.
-
-
1 QP with all the supervisors and all the teams >> RBAC will make sure the supervisor is getting only the evaluations relevant to their team.
-
-
Users are not be able to evaluate themselves since they don't usually have Evaluation view on their own team.
Create Interaction-Segment-Based Views
Create views based on interaction-segments to restrict access to data related to segments. This includes recordings and chat transcripts routed through ACD as well as data from any digital channels in DFO.
- Click the app selector
and select Admin.
- Go to Security Settings > Views.
- Click New View.
- Enter a View Name and a Description.
-
Select Interaction-Segment as the Type to restrict access to data related to segments.
- In the Interaction From drop down, select Teams or Skills.
- In the Teams drop-down, select each team whose data you want employees to be able to access when they are assigned to this view.
- In the Skills drop-down, select each skill whose data you want employees to be able to access when they are assigned to this view.
- Click Create.
Create Role-Based Views
Create views based on roles to restrict access to data related to roles, such as Supervisors or Agents.
- Click the app selector
and select Admin.
- Go to Security Settings > Views.
- Click New View.
- Enter a View Name and a Description.
-
Select Role as the Type to restrict access to data related to roles.
- In the Roles drop-down, select each role whose data you want employees to be able to access when they are assigned to this view.
- Click Create.
Create User-Based Views
Create views based on users to restrict access to data related to other employees in your organization, such as their names.
- Click the app selector
and select Admin.
- Go to Security Settings > Views.
- Click New View.
- Enter a View Name and a Description.
-
Select User as the Type to restrict access to data related to users.
- In the Users From drop-down, select Hierarchies, Scheduling Units, or Teams.
- In the Hierarchies / Nodes drop-down, select which parts of the hierarchy whose data you want employees to be able to access when they are assigned to this view. You can expand or collapse each section of the hierarchy until you find the part that you need. Selecting a parent node will provide access to that node and all of its descendant nodes.
- In the Scheduling Units drop-down, select each scheduling unit whose data you want employees to be able to access when they are assigned to this view.
- In the Teams drop-down, select each team whose data you want employees to be able to access when they are assigned to this view.
- Click Create.
Assign Views to Employees
You can assign views to employees manually in the employee profile. You can also assign them with the bulk upload employee template.
- Click the app selector
and select Admin.
- Click Employees.
- Locate the employee you want to assign a view to. Click to open the employee profile.
- Click Visibility.
-
In the Select Views drop-down, select the views you want to give the employee.
- Click Apply, then click Save.
- Continue assigning views to employees as needed.