Manage Data Access with Views

You can create views to control access to the following kinds of data:

You can choose how access to ACD data is restricted. You can restrict it by teams or by campaigns.

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. Users can have multiple views assigned to them.

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. Only select the evaluations you want your assigned users to be able to view. All the evaluations not included in the view will be hidden from the assigned users.

Evaluation-Based Views takes preference over any other views that may have been created, such as Interaction-Based View or User-Based View.

If an employee has the Play/Download Recordings permission, an Evaluation-Based View also grants the employee access to play back the segments associated with the view's teams. Access granted this way applies only to those segments, not to the entire contact, see How Playback Access Works for Evaluation and Interaction Segments Views.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Evaluation as the Type to restrict access to data related to evaluations.
  6. 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. Select the teams to be included in the view criteria. Because this list can be extensive, only the first 200 teams are loaded by default. Scroll to load more teams incrementally, or use the search bar to quickly locate and select specific teams from your entire organization.
  7. Click Create.

Tips for QM Flows

  1. Using only the Evaluations view:

    1. Will restrict evaluations.

    2. Will enable the playback of the associated interactions.

    3. 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 play back all interactions but only take the quality action for the interactions that belong to their teams.

  2. In addition, if you want your agents to see only their own interactions in their Interaction application use Interaction View.

  3. Minimize the maintenance of multiple QPs and let Role-Based Access Control (RBAC) restrict who is doing what with one or more QPs.

    As an example:

    • 3 supervisors or evaluators

    • 3 teams defined

    • 3 views—one per team

      • Associate the relevant view to the appropriate supervisor by the relevant team.

    • 1 QP with all the supervisors and all the teams. RBAC will make sure each supervisor is getting only the evaluations relevant to their team.

  4. Users are not be able to evaluate themselves since they don't usually have the Evaluation view on their own team.

How Playback Access Works for Evaluation and Interaction Segments Views

Evaluation-based views and Interaction Segment-based views both control which recording segments a user can play back, in the Player application or through the Media Playback API.

When you assign more than one of these views to an employee, CXone combines the teams and skills covered by all of them to determine what the user can play back. Users also need the Play/Download Recordings permission. Without this permission, neither view type grants any playback access.

By default, these views grant access at the segment level. A user can play back a segment only if the user has access — through their own team assignment or through an assigned view — to the team or skill associated with that segment.

To play back an entire contact, rather than only the individual segments the employee can access, one of the following must be true:

  • The employee has access to every team or skill associated with each of the contact's segments.

  • The Allows users to access all segments in the interaction for the selected teams/skills checkbox is selected on the Interaction-Segment-Based View assigned to the employee that includes access to at least one of the contact's segments.

Create Hours-of-Operation-Based Views

Create views based on hours of operation to restrict access to those records. Only select the records you want users assigned to the view to be able to access. All the records not included in the view will be hidden from those assigned users.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Hours of Operation as the Type to restrict access to hours of operation records.
  6. In the Hours of Operation drop-down, select the records you want users to be able to view.
  7. Click Create.

Create Interaction-Segment-Based Views

Create views based on interaction segments to restrict access to data related to segmentsClosed A stage in the interaction, such as when a call is transferred to another agent, or agents speak internally to consult.. This includes recordings and chat transcripts routed through ACD, as well as data from digital channelsClosed Various voice and digital communication mediums that facilitate customer interactions in a contact center. . You can choose to filter interaction-segment views by team or ACD skills. You cannot filter these views by channel.

When setting up views that filter interactions on digital channels: 

  • Filtering by team or skill affects the interactions that users with the view can access:
    • Team: Users can see interactions last handled by an agent on the selected team. For digital interactions, they can also see interactions that no agent has handled yet. This means that all teams can see interactions that haven't been handled. Filtering by team does not provide a strict separation of interactions.
    • Skill: Users only see interactions associated with the selected ACD skill or skills. Filter by skills when you need to restrict access to specific interactions.
  • All users assigned to the view must have the Digital Engagement attribute enabled in their employee profile. Users who do not have this attribute can see all interaction data, even if the view restricts access to it.

Only select the teams or skills whose interactions you want users assigned to the view to be able to access. All the interactions handled by teams or skills not included in the view will be hidden from those assigned users.

The interaction segment view is the only type of view that applies to digital interactions. Other views, including others that restrict access to data by teams or ACD skills, do not restrict access to digital interaction data.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Interaction-Segment as the Type to restrict access to data related to segmentsClosed A stage in the interaction, such as when a call is transferred to another agent, or agents speak internally to consult..

  6. In the Interaction From drop-down, select Teams or Skills.
  7. 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.
  8. 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.
  9. Click Create.

Create Role-Based Views

Create views based on roles to restrict access to data related to roles, such as Supervisors or Agents. Only select the roles you want users assigned to the view to be able to access. All the roles not included in the view will be hidden from those assigned users.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Role as the Type to restrict access to data related to roles.

  6. 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.
  7. Click Create.

Create Script Folder-Based Views

These views allow you to restrict access to the folders in NiCE CXone where Studio scripts are stored. For each view, only select the folders that you want to be accessible to users assigned to that view. Use views in combination with workflow stage permissions to manage the security of your scripts. Users can see scripts and script folders they have access to on the Scripts page in Studio.

Views are only supported in NiCE CXone Studio. They are not supported in Desktop Studio.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Script Folders as the Type.
  6. Click Open Script Folder Options.
  7. On the Select Script Folders window, click each script folder that you want users with this view to be able to access.
  8. Click Confirm.
  9. 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. You can control access according to hierarchies, scheduling units, or teams. Only select the hierarchy or node, scheduling unit, or team you want users assigned to the view to be able to access. Everything not included in the view will be hidden from those assigned users.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select User as the Type to restrict access to data related to users.

  6. In the Users From drop-down, select Hierarchies, Scheduling Units, or Teams.
    • In the Hierarchies / Nodes drop-down, select which parts of the hierarchy 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. The number of subnodes is listed next to each parent node in the drop-down.
    • 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.
  7. Click Create.

Create Workflow-Data-Based Views

Create views based on workflow data to restrict access to those records. Only select the records you want your assigned users to be able to view. All the records not included in the view will be hidden from those assigned users.

  1. Click the app selector icon of app selector and select Admin.
  2. Go to Security Settings > Views.
  3. Click New View.
  4. Enter a View Name and a Description. For the description, use plain text only. URLs or markup such as HTML will not be saved.
  5. Select Workflow Data as the Type to restrict access to data related to workflow data.
  6. In the Workflow Data Items drop-down, select the records you want users to be able to view.
  7. Click Create.

Create Global View

The Global View is designed to enforce data accessibility by Teams and Skills. It ensures users have access only to the data they are allowed to view, regardless of which entity they are querying about.

Data access is restricted by Teams and Skills. This ensures users can only access data relevant to their assigned teams and skills as defined in the User Hub.

Global View is applicable to NiCE CXone Actions, Copilot for Supervisors and Dashboard.

This view provides a streamlined and secure way to manage data visibility. It ensures users have access only to the data they need.

To create a Global View

  1. Click the app selector icon of app selector and select Admin.

  2. Navigate to Security Settings > Views.

  3. Click New View.

  4. Enter a View Name. Optionally, add a Description.

  5. From the Type drop-down, select Global.

  6. Choose Skills or Teams from the View Data From drop-down to limit data access.

  7. Click Create. The new view appears in the Views list.

A Global View takes around 45 minutes to become effective after an assignment.

Users can access data from various NiCE CXone applications, such as QM, PM, and Interaction Analytics (CXone), without being limited by individual application restrictions. However, accessing data from Copilot for Supervisors and Actions depends on the Global View configuration in the Admin application.

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.

  1. Click the app selector icon of app selector and select Admin.
  2. Click Employees.
  3. Locate the employee you want to assign a view to. Click to open the employee profile.
  4. Click Security.
  5. In the Views drop-down, select the views you want to give the employee.

  6. Click Apply, then click Save.
  7. Continue assigning views to employees as needed.