Professional Documents
Culture Documents
Release 3.1
385A0427-04 Rev. A2
TM
Information in this document is subject to change without notice and does not represent a commitment on the part of NICE Systems Ltd. The systems described in this document are furnished under a license agreement or nondisclosure agreement. All information included in this document, such as text, graphics, photos, logos and images, is the exclusive property of NICE Systems Ltd. and protected by United States and international copyright laws. Permission is granted to view and photocopy (or print) materials from this document for personal, non-commercial use only. Any other copying, distribution, retransmission or modification of the information in this document, whether in electronic or hard copy form, without the express prior written permission of NICE Systems Ltd., is strictly prohibited. In the event of any permitted copying, redistribution or publication of copyrighted material, no changes in, or deletion of, author attribution, trademark legend or copyright notice shall be made. All contents of this document are: Copyright 2008 NICE Systems Ltd. All rights reserved.
This product is covered by one or more of the following US patents:
4,893,197 5,396,371 6,115,746 6,330,025 6,785,370 6,959,079 7,203,655 5,185,780 5,446,603 6,122,665 6,542,602 6,856,343 6,965,886 7,240,328 5,216,744 5,457,782 6,192,346 6,564,368 6,865,604 6,970,829 7,305,082 5,274,738 5,819,005 6,246,752 6,694,374 6,870,920 7,010,106 7,333,445 5,289,368 5,911,134 6,249,570 6,728,345 6,871,229 7,010,109 7,346,186 5,325,292 5,937,029 6,252,946 6,775,372 6,880,004 7,058,589 7,383,199 5,339,203 6,044,355 6,252,947 6,785,369 6,937,706 7,085,728 7,386,105
360o View, ACTIMIZE, Actimize logo, Alpha, Customer Feedback, Dispatcher Assessment, Encorder, eNiceLink, Executive Connect, Executive Insight, FAST, FAST alpha Blue, FAST alpha Silver, FAST Video Security, Freedom, Freedom Connect, IEX, Interaction Capture Unit, Insight from Interactions, Investigator, Last Message Replay, Mirra, My Universe, NICE, NICE logo, NICE Analyzer, NiceCall, NiceCall Focus, NiceCLS, NICE Inform, NICE Learning, NiceLog, NICE Perform, NiceScreen, NICE SmartCenter, NICE Storage Center, NiceTrack, NiceUniverse, NiceUniverse Compact, NiceVision, NiceVision Alto, NiceVision Analytics, NiceVision ControlCenter, NiceVision Digital, NiceVision Harmony, NiceVision Mobile, NiceVision Net, NiceVision NVSAT, NiceVision Pro, Performix, Playback Organizer, Renaissance, Scenario Replay, ScreenSense, Tienna, TotalNet, TotalView, Universe, Wordnet are trademarks and registered trademarks of NICE Systems Ltd. All other registered and unregistered trademarks are the property of their respective owners. Applications to register certain of these marks have been filed in certain countries, including Australia, Brazil, the European Union, Israel, Japan, Mexico, Argentina and the United States. Some of such registrations have matured to registrations.
385A0427-04 Rev. A2
For assistance please contact your local supplier or the nearest NICE Systems Customer Service Center:
EMEA Region: (Europe, Middle East, Africa) Tel: +972-9-775-3800 Fax: +972-9-775-3000 email: support@nice.com APAC Region: (Asia/Pacific) Tel: +852-8338-9818 Fax: +852-2802-1800 email: support.apac@nice.com The Americas Region: (North, Central, South America) Tel: 1-800-NICE-611 Fax: +720-264-4012 email: support.americas@nice.com Israel: Tel: 09-775-3333 Fax: 09-775-3000 email: support@nice.com
NICE invites you to join the NICE User Group (NUG). Visit the NUG Website at www.niceusergroup.org, and follow the instructions.
For general information on NICE Systems products please contact your local distributor or the nearest NICE Systems office:
International Headquarters-Israel Tel: +972-9-775-3100 Fax: +972-9-775-3070 email: info@nice.com United Kingdom Tel: +44-8707-22-4000 Fax: +44-8707-22-4500 France Tel: +33-(0)1-41-38-5000 Fax: +33-(0)1-41-38-5001 North America Tel: 1-800-663-5601 Fax: +201-356-2197 email: na_sales@nice.com Germany Tel: +49-(0)-69-97177-0 Fax: +49-(0)-69-97177-200 Hong-Kong Tel: +852-2598-3838 Fax: +852-2802-1800
Please send all queries, comments, and suggestions pertaining to this document to
nicebooks@nice.com
Contents
1
Introducing the Users Administrator 11
Opening the Users Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Navigating the Users Administrator Window. . . . . . . . . . . . . . . . . . . . . . . . . 14 Folders Pane Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Searching/Filtering the Users and Groups Lists . . . . . . . . . . . . . . . . . . . . . 16 Running a Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Adding a User from the Search Results to a Group . . . . . . . . . . . . . . . . 20 Contents Pane Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Defining User Name Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Showing/Hiding Deleted Users Details in the Users Administrator . . . . . . . 23 Details Pane Highlights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2
Overview and Getting Started 27
Overview of NICE Perform Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 What is an Organization? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Who are the Users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 How are System Users Authenticated? NICE Perform vs. Active Directory . 32 Active Directory System User Highlights . . . . . . . . . . . . . . . . . . . . . . . . 32 Which Agent Identification Should I Use? Agent ID vs. Extension . . . . . . . . 33 User Details and Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 What is a Group?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Rules of Group Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Displaying Group Details and Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 What is a Profile? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Rules of Profile Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Contents NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 5
Displaying Profile Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Defaults Provided with NICE Perform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Getting Started Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 About Imported User Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3
Profiles 49
Guidelines for Creating and Attaching Profiles . . . . . . . . . . . . . . . . . . . . . . . 50 Before you Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Creating a New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Assigning Privileges for Business Data Fields . . . . . . . . . . . . . . . . . . . . . . . 60 Changing Profile Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Attaching Profiles to Users, Group Members, or Group Managers . . . . . . . 66 Deleting a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4
Users - Agents, Traders, and System Users 71
Before you Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Adding a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Displaying User Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Customizing a System User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Changing Login Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Manually Resetting Someone elses Login Password and Name . . . . . . 82 Automatically Resetting Someone elses Login Password . . . . . . . . . . . 83 Manually Resetting your own Login Password . . . . . . . . . . . . . . . . . . . . 83 Automatically Resetting your own Login Password . . . . . . . . . . . . . . . . 84 Changing Login Name and Password (Active Directory) . . . . . . . . . . . . . . . 85 Changing Password Expiration Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Deactivating or Reactivating a Login ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Deactivating or Reactivating a Login ID (Active Directory) . . . . . . . . . . . . . 89 Attaching Profiles to System Users and Displaying Privileges . . . . . . . . . . . 89 Adding an Agent Identity (First-Time and Multiple) . . . . . . . . . . . . . . . . . . . 91 Deleting a User Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Showing/Hiding Deleted Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Contents NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 6
5
Groups 95
Before you Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Creating a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Adding Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Removing Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Defining a Group Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Attaching Profiles to Group Members and Group Managers . . . . . . . . . . . 104 Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
A
Customizing Organization Settings 105
Defining Password Policy for System Users . . . . . . . . . . . . . . . . . . . . . . . . 106 Password Policy Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Defining Security for NICE Perform Applications . . . . . . . . . . . . . . . . . . . . 110 Login Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Defining Target Number of Evaluations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Defining the Domain Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
B
Tips and Tricks 117
To Display Details of Last Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 To Change the User Name Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 To Create a List of Invalid Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 To Limit Invalid Login Attempts (Account Lockout) . . . . . . . . . . . . . . . . . . 119 To Add a New User to an Existing Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 119 To Deactivate or Reactivate a System User Login ID . . . . . . . . . . . . . . . . . 119 To Add System User Status to an Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 To Record a System Users Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 To Define the Agent Identification for Screen Recording . . . . . . . . . . . . . . 120 To Create a Limited All Users Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Contents NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 7
Deleted Users are/are not Appearing in User Lists in Other Applications . 122 Active Directory System Users cannot Log in to NICE Perform . . . . . . . . . 122 Email for System-Generated Password is not Received by User . . . . . . . . 122 Profile Changes are not Activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Some or all of the Agents (Traders) are Missing . . . . . . . . . . . . . . . . . . . . 123 Some Agent (Trader) Information is Missing . . . . . . . . . . . . . . . . . . . . . . . 123 Some Functionality is not Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
C
Profile Privileges 125
Guidelines and Tips for Creating Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 127 User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Group Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Applications Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 System Administrator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Users Administrator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Business Analyzer Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Form Designer Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Monitor Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 ROD (Recording On Demand) Privileges . . . . . . . . . . . . . . . . . . . . . . . . . 138 Reporter Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Lists Editor Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Rules Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Lexicon Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 My Universe Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 ScreenSense Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Backup Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Insight Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Player Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Business Services Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 ClearSight Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Channel Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Interaction Data Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Selecting and Filtering Interaction Data Privileges . . . . . . . . . . . . . . . . . . 149
Contents NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 8
Reporter Categories Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Form Groups Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Query Folders Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
D
Sample Contact Center 153
Overview of a Sample Contact Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Sample Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Working the System - Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Glossary Index
159 161
Contents NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
1
Introducing the Users Administrator
Welcome to the Users Administrator! - This application streamlines user management by providing tools for establishing site security, user authentication, and agent identification. Users logging in to NICE Perform must have proper authorization for each application, as well as permission to access agents and their interactions. The Users Administrator provides the means to give each user an individual Login ID with the necessary privileges. Password and security options can be set globally, or on an individual basis. NICE Perform also supports Active Directory authentication. Privileges are profile-based. Each profile is a set of privileges. Profiles are attached to users or to groups of users. Profiles that are attached to a group, give each user in the group identical privileges. Each time the privileges in a profile are updated, the change is dynamically filtered throughout your user database. Each time a user is added to or removed from a group, the users privileges are automatically adjusted to reflect their new position. Users can be grouped together for managerial purposes. NICE Perform supports a multi-tiered user hierarchy. The Users Administrator supports data integrity by restricting data access and manipulation to a need-to-know basis. View, Edit, and Query privileges to agent information and interaction data are each granted separately. Interactions must be associated with the agent involved. The Users Administrator provides the means to uniquely identify each agent and their interactions. This guide describes how to build your organizations employee hierarchy and assign privileges to users as necessary. A sample organizational structure and examples are provided along the way. A complete list of all available privileges is provided in the appendices.
IMPORTANT This guide describes complete functionality of the application. Your ability to use the system is dependent on your site configuration and your own access privileges. Some fields and functions might not be available.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
11
Contents
Opening the Users Administrator ................................................................................. 13 Navigating the Users Administrator Window............................................................... 14 Folders Pane Highlights................................................................................................. 15 Searching/Filtering the Users and Groups Lists......................................................... 16 Contents Pane Highlights ..............................................................................................21 Defining User Name Format ...................................................................................... 21 Showing/Hiding Deleted Users Details in the Users Administrator ............................ 23 Details Pane Highlights .................................................................................................. 25
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
12
Log in to the NICE Perform Compliance Suite. From the Accessories menu, select Users Administrator.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
13
Folders Pane
Contents Pane
Details Pane
Folders Pane
Displays the Organization tree. Click a branch to display its contents in the Contents pane. Click the Groups branch to expand it and display its contents in this pane. The Folders pane can be collapsed and hidden. Displays the contents of your selection in the Folders pane. The Contents pane can be collapsed and hidden. The Contents pane displays the following according to your selection:
If you select... All Users The Contents Pane displays...
Contents Pane
All the users in all the groups, including subgroups. All users are displayed in one flat layer. All the profiles that are attached to the logged-in user. (Directly or Inherited) The results of your most recent search.
Shows the contents of your selection from the Folders/Contents pane. This is the area where you enter data and create your organization.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
14
To quickly locate users or groups in the Organization tree, click the Search folder. Users located using a search operation, can be dragged and dropped into groups in the folders list. For details, see Adding a User from the Search Results to a Group on page 20. Expand the Organization tree and click an item to fill the Contents pane or to display the items details in the Details pane. To create a new user, group, or profile, click the New dropdown arrow and select New User, Group, or Profile.
-or-
Click the All Users, Groups, or Profiles branch, and then click New.
Folders cannot be added to the Organization tree at the level of the All Users or Groups branches. Groups can be moved around in the groups tree using the drag-and-drop technique. Groups that were imported using the Importer cannot be moved. To delete an item from the Organization tree, select it and click Delete. The name of the All Users or Groups branches can be changed by the SuperUser. Select them and click Edit. The names of individual Groups can be changed. Select a group and click Edit.
NOTE: All documentation uses the default folder names. We recommend that you change folder names only when absolutely necessary and then try to maintain part of the original folder name. Example: Change All Users to All Users (Home office).
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
15
Click the appropriate arrow to hide or open the Folders pane (shown below).
You have an extension number and want to locate the user. You want to locate all the groups with a specific profile.
TIP:
When creating a new user, you may want to search for an existing Agent ID or extension to verify that it is not already in use. Search results are contingent on your allocated privileges. For example, an Agent ID or extension may already be in use, but will not display if you do not have permissions to view this agents details.
Search results are saved in the Search Results tab until the next Search or until the user logs off. They are not saved from one session to the next. Use the following tips as guidelines.
Tip Example
Search criteria are not case-sensitive. Users first and last names are searched separately. Use the asterisk * as a substitute for zero or more characters. Use the question mark ? as a substitute for a single character. To search for an asterisk or question mark, enter a backslash \ before the asterisk or question mark.
Enter mary jane to search for Mary Jane. Enter frank to search for Frank Smith and Robert Frank. Enter R* to search for names that begin with R (Ronald Smith and Brent Reese will be found). Enter Sales Group? to search for similar group names such as Sales Group1, Sales Group2, etc. In this example, Sales Group10 will not be found. Enter Lost\*Found to search for Lost*Found.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
16
Remember: The asterisk (*) is used as a substitute for zero or more characters. The question mark (?) is used as a substitute for a single character.
IMPORTANT If you do not enter an asterisk in the search field, then only exact matches will be found. Example: If you run a Groups search for Sales, then Sales Managers will not be found. If you search for Sales*, then it will be found.
Running a Search
A Search can be run on either the list of Users or the list of Groups. Separate searches must be run for the users and for the groups lists. If deleted users are not hidden in the System Administrator, then they will appear in the Search Results if they match the search criteria.
To search the lists or Users or Groups: 1.
In the Folders pane, click Search. The Search details appear. The Quick Search window appears.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
17
2.
To search the Users list, click the Users tab and define search criteria.
option from the list, a date field opens. If you click the date field, a selection calendar appears.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
18
3.
To search the Groups list, click the Groups tab and define search criteria.
option from the list, a date field opens. If you click the date field, a selection calendar appears.
4. 5.
Click
The search results are displayed in the Results tab and in the Contents pane as shown below.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
19
6. 7. 8.
Double-click an item to display its details. To add a user to group as a group member, see Adding a User from the Search Results to a Group on page 20. Click Search at any time to see the results of your latest search. Search results are saved in the Search Results tab until the next Search or until the user logs off. They are not saved from one session to the next.
You want to add the user whose Agent ID is 1234 to the Sales group. Run a search specifying 1234 as the Agent ID. Then drag and drop the resulting user into the Sales group. For more information about group members, see Adding Group Members on page 100.
To add a user from the Search Results to a Group: 1. 2. 3. 4.
Run a Search to locate the user. See Running a Search on page 17. In the Folders pane, expand the Groups branch so that the target group is shown. In the Folders pane, click Search. Then click the Results tab. In the Search Results list, select a user and drag and drop it to the group in the Folders pane. The selected user automatically becomes a member in the selected group. To give the user managerial status, see Defining a Group Manager on page 102.
5.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
20
N/A
System User
(has a monitor)
Deleted User
N/A
Click a user or profile to display its details in the Details pane. Click the appropriate arrow to hide or open the Contents pane (shown below).
Select an option in the Contents pane. When the Contents pane is hidden, use the Scroll buttons located at the top of the Details pane to navigate the Contents list and display the next/previous item.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
21
EXAMPLE:
Select Organization and then click the Settings tab. Expand the Display section.
Expand
2. 3.
In the Full Name area, select the parts of the name to be displayed. To change the order of the names, use the up and down arrows. In the First Separator and Second Separator fields, enter separators to appear between the first and second, and between the second and third names. To leave a space between names, leave the appropriate box blank. Click . Changes take effect immediately. Reports that have already been created and saved, will not be changed.
4.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
22
Users who are deleted from the Organization can still be displayed in user lists. Showing deleted users allows you to select them as query criteria and to play back their interactions. A retention period is defined for deleted users. This is the period of time during which a user is considered a deleted user. The retention period is defined once for all applications except for the Reporter. It is defined separately for the Reporter application. Defining to show or hide deleted users is application-specific. For example, you can select to hide all deleted users in the Users Administrator application and to show all deleted users in the PBO Requests application. In the Organization settings, you define the show/hide status for the Users Administrator, and the retention period for all applications. Changing the show/hide option takes effect immediately. There is no need to restart a server or to log off and log in again to NICE Perform.
IMPORTANT User records are never actually deleted from the User database, even if they are not currently shown, or not within the defined retention period. EXAMPLE:
Betty is deleted from the Organization on January 1. The retention period for All applications is 3 months. For Reporter it is 12 months. In applications where Show Deleted Users is selected, Betty will appear in the Users list until March 31. In the Reporter, Betty will appear until December 31. For Betty to appear in April, change the Retention period for All applications to 4 months.
Select Organization and then click the Settings tab. Expand the Display section.
Expand
2.
To show deleted users in the Users Administrator, select the Show deleted users details in Users Administrator checkbox.
Chapter 1: Introducing the Users Administrator 23
-or-
To hide deleted users in the Users Administrator, clear the Show deleted users details in Users Administrator checkbox.
3.
User records will never be deleted from the User database, even after this retention period. The maximum value for retention period is 99 months.
4. 5.
Click . All deleted users will be shown/hidden in all areas of the Users Administrator application as indicated. In other applications, select the Show Deleted Users checkbox to display the users deleted within the retention period.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
24
Click Click
after each change. to undo all changes since your last save. to return to the group (or all users list) from which you
If the Details pane contains a list of users, groups, or profiles, double-click an item to open its details.
Chapter 1: Introducing the Users Administrator NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
25
2
Overview and Getting Started
NICE Perform is designed to enable your users to record, play back, and store your employees interactions. Agents (traders) whose interactions are recorded must be defined in the NICE Perform system. Permission, in the form of privileges, are required by all users who will be using NICE Perform applications in any manner. This includes the functions mentioned previously as well as setting recording schedules, creating reports, and managing the user database and other resources.
Contents
Overview of NICE Perform Hierarchy ........................................................................... 28 What is an Organization?............................................................................................... 30 Who are the Users? ........................................................................................................ 31 How are System Users Authenticated? NICE Perform vs. Active Directory .............. 32 Which Agent Identification Should I Use? Agent ID vs. Extension............................. 33 User Details and Profiles............................................................................................ 34 What is a Group? ............................................................................................................ 37 Rules of Group Hierarchy........................................................................................... 37 Displaying Group Details and Profiles........................................................................ 38 What is a Profile? ...........................................................................................................40 Rules of Profile Inheritance ........................................................................................ 40 Displaying Profile Privileges....................................................................................... 42 Defaults Provided with NICE Perform........................................................................... 43 Getting Started Workflow............................................................................................... 46 About Imported User Databases ................................................................................... 47
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
27
Inherited Privileges
ed
Group
Manager
Each employee must be defined as a User. There are two types of users: System Users and Agents (Traders). Each employee can be defined as one or both types of users.
System Users are users who log in to and use NICE Perform applications. System users can be
given permission to set up recording schedules, playback interactions, and manage other users in the system. System users whose interactions are recorded must also be defined as agents.
Agents (Traders) are users whose interactions are recorded. This includes traders, brokers, or back office personnel. All agents are recognized by one or more unique IDs. The method of assigning a unique ID varies with each system and are described in Which Agent Identification Should I Use? Agent ID vs. Extension on page 33. Traders may not be aware that they are connected to a NICE Perform system. Traders who access any of the NICE Perform applications, such as Playback Organizer, must be defined as system users. Groups of users (system users and/or traders) can be created. This allows you to assign the same
profiles to a group of users or to include a group of agents in a profile, giving the receiver of the profile access to all of the groups agents interactions. Each group can have one or more managers (supervisors). A groups managers can be assigned different profiles from the groups members, giving them privileges over the groups members.
Profiles are created and attached to groups or users. Each profile is a set of privileges to different applications or groups and users.
To use an application in the system and to access traders interactions, a user must be defined as a system user and be assigned a profile containing the necessary privileges. Profiles can be attached to a group or directly to a user. Profiles that are attached to a group are inherited by all the groups members.
About Privileges Privileges are assigned by creating a profile which contains a set of privileges. The profile is
attached to the users who are to receive its privileges. If the privileges of a profile change, all the users who have that profile are automatically affected. Profiles can be attached either to an entire group, just its managers, or to individual users. Profiles are simplest to track when attached at group level.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
28
The applications they will be using and the tasks within each application that they require. The users (traders and/or system users) they are managing. Do this through a group. The reporter categories for reports they will manage. The Query folders for queries they will edit or run. The Data fields they need to view.
NOTE: NICE Perform comes with a predefined profile to view and query the most common data fields. It is called Basic Columns and is attached to the All Users group. Add additional query and edit privileges in a separate profile as needed.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
29
What is an Organization?
What is an Organization?
NICE Perform consists of one organization. The structure of your organization can be viewed in the folders pane. It is the root of your folders list. Password and security options are set at organization level. See Customizing Organization Settings on page 105. Some password and security options can be overridden at individual user level. See Customizing a System User on page 80.
In the Users Administrator, your organization is divided into the following hierarchy:
All Users
A single master folder which gives you direct access to all the users in your system. Profiles with the most basic privileges can be attached at this level. Example: Give each user the privilege to playback their own interactions: Create a profile giving this privilege to the Self user and attached it at this level. Contains all groups and their subgroups. Contains all profiles for the system. Search criteria and results.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
30
manage and supervise other users and the system. System users log in to NICE Perform applications using a unique login ID. For an overview of the different methods of identification, see How are System Users Authenticated? NICE Perform vs. Active Directory on page 32.
Agents (Traders) are users whose interactions can be recorded, stored, and played back. Each Agent (Trader) must be uniquely defined in the system. For an overview of the different methods of identification, see Which Agent Identification Should I Use? Agent ID vs. Extension on page 33.
The system comes with several predefined users. For a list and descriptions of all predefined users, see Default Users on page 43.
NOTE: To allow an agent to log in to applications the agent must be defined as a system user with appropriate privileges.
A user created in the system can appear in one or more of the following places within the Users Administrator:
Group Member - allows the user to receive profiles assigned to the group and to be managed as
part of a group.
Group Manager - allows the user to receive profiles over a dynamic group of users. User Listed as a Resource List of a Profile - defines a user as an entity in a profile. A user
defined as an entity within a profile does not receive permissions of the profile. As an entity within a profile, this users interactions can be recorded, played back, evaluated, or calibrated by the system user allocated this profile.
TIP: Add users to groups and then add the group to a profile. Creating groups with members and managers allows you to attach profiles to a job position instead of directly to a user. Thus employees can move between groups or change positions and always receive the privileges required for their position.
EXAMPLE:
Trader Tom is listed as a resource in the Manager profile in the user resource list with view and play privileges selected. The Manager profile includes privileges for the Playback Organizer application. System User Sue has the Manager profile. Sue can now play back Toms interactions. Given this profile, Sue has the combined privileges for Playback + Tom. Tom does not benefit directly from this profile.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
31
How are System Users Authenticated? NICE Perform vs. Active Directory
System User Authentication is the process of identifying System Users who try to log in to NICE Perform applications. The NICE Perform system must determine the authenticity of the user login name. The NICE Perform system users can be configured to be authenticated in one of two ways:
NICE Perform Authentication - Each system user is defined in the NICE Perform system by a unique login name. The user uses this login name, and the password defined with it, to log
Directory Authentication. Each system user is defined in the Active Directory at your site by a unique Windows User Name and Domain. The user is then defined in NICE Perform with the exact same Windows User Name and Domain. NICE Perform uses the values in the Active Directory to authenticate each system user. In this environment, you do not define an additional login name and password in NICE Perform, since the users actual Windows User Name and password defined in the Active Directory are used to log in to NICE Perform. The link between NICE Perform and the Active Directory is according to Domain and Windows User Name. These must be unique for each user. (Duplicate Windows User Names are allowed if they are in different domains.) Passwords are according to the Active Directory. A user, defined in NICE Perform that is not in Active Directory, cannot log in to NICE Perform. A user, defined in Active Directory and not in NICE Perform, cannot log in to NICE Perform.
In the Active Directory environment, the System User tab is hidden and the User is a System User checkbox is located in the General tab. This is because login information and password policy are defined in the Active Directory.
This is where the System Users identification is defined
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
32
The General tab of the All Users branch features a Validate button. You can select users and then click the Validate button to confirm whether the selected users identification is valid in the Active Directory. Validate will not create a user definition in Active Directory. It will only confirm whether the selected users identification (Windows User Name and Domain) exists in Active Directory. An invalid user definition indicates that the Windows User Name/domain combination defined in the Users Administrator is not found in Active Directory. This user will not be able to log in to NICE Perform.
Invalid User
Valid User
The validation results are shown only while this view is displayed. If you switch views (open a user definition) and return to this view, the validation results will not appear.
Organization Branch
In the Organization branch, there are the following changes from the standard interface for Active Directory authentication environment:
Security tab - removed tab because the password policy is determined by the Active
Directory.
Settings tab - the Security Options section does not appear because it is determined by the
Active Directory.
Domains tab - appears so that you can define the available domains for your user definitions.
Each agent must be defined with a unique Agent Identification value, which links each agent to his or her own interactions. Depending on your site configuration, this unique Agent Identification may be defined as Agent ID or Extension. In addition, when performing screen recording at sites comprised of multiple branches, you must define the Agent Identification for Screen Recording value. This section provides an overview of each of these agent identification values.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
33
Agent ID
Each agent (trader) must have a unique Agent ID for NICE Perform, separate from the Windows ID. An agent ID cannot be more than 32 characters. Agents must log in at the beginning of their shift and log out at the end of their shift. Login can be done via the agents telephone receiver or computer screen. Once an agent logs in, all interactions made from that telephone and/or computer are attributed to the agent until logout. In sites with more than one switch, an agent can have more than one Agent ID. In some sites, the Windows username is used for agent identification. The agent logs in to Windows and is automatically identified by NICE Perform. In this case, when defining an agent in the Users Administrator, enter the same unique ID in both the Windows User Name and the Agent ID fields. Agent ID is popular in contact centers where many agents are using the same station on different shifts and where one agent may work from a different station on each shift.
Extension
Each agent (trader) is assigned a single telephone extension. All interactions via the extension are attributed to agent. Extension identification is popular in banks and on trading floors where agents (traders) always work from the same location. An extension ID cannot be more than 20 characters.
Agent Identification for Screen Recording
In environments where screens from more than one branch are being recorded, to avoid duplicate users, define the Agent Identification for Screen Recording value (Agent tab). This value represents a unique branch at your site is defined unique per site. Users Administrator associates this value with your Windows username, creating a unique user for every user defined in your system. For more information, see Branch Site Support in the NiceScreen Installation Guide.
General Details
Includes the users personal details and a list of all the groups to which the user directly belongs. Contains personal data such as hire date, department, and job position codes. This information is used for reporting and querying purposes.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
34
System User Used to define the user as a system user. System users can log in to NICE
Perform applications according to their privileges. In the Active Directory environment, the System User tab does not appear. In this environment, you define a user as a system user in the General tab.
Agent
Used to define the users identity - associated by Switch ID or Extension. Agents interactions are recorded by NICE Perform. The Agent Identification field enables you to define a unique identifier for your site. This option is only necessary when defining agents for a multibranch site, and screen recording is performed at multiple branches. This value ensures that each agent is uniquely identified. For more information about multibranch sites, see Branch Site Support in the NiceScreen Installation Guide.
Profiles
Includes a list of all profiles attached to the user (directly and inherited). Allows you to view all profile privileges in combination.
To display a users details: 1. In the Folders pane, click All Users. A list of users appears in the Contents pane and in the
Details pane.
2. Double-click a users name. The users details appear in the Details pane. 3. In the Profiles list, select one or more profiles. Then click
The combined privileges from all selected profiles are shown in the Profile Privileges area.
Direct Profile Click Show Privileges View results here Inherited Profile
NOTE: If No Profile Assigned appears in the Profile Privileges title bar, it means you did not select a profile, or you did not click Show Privileges, or the profiles selected are empty and do not contain any privileges.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
35
TIP:
When you click All Users in the Folders pane, group details for all the users appear in the Details pane. All Users is considered a group and profiles can be attached system-wide at this level. Use the scrolling arrows located at the top of the Details pane to navigate the Contents list and display the next/previous users details:
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
36
What is a Group?
What is a Group?
A group unites users for the purpose of attaching the same profiles to all the users, and/or to allow them to be managed by the same manager(s). Profiles attached to a manager of a group, give the manager privileges over the groups members.
TIP: Add users to groups. Creating groups with members and managers allows you to attach profiles to a job position instead of directly to a user. Thus employees can move between groups or change positions and automatically receive the privileges required for their position.
Create groups whose members all need to receive the same profiles (privileges). Create groups whose members all need to be attached to the same profile as a resource. These groups do not necessarily need to have any profiles of their own.
EXAMPLE:
Supervisor Steven wants to record all the calls of all agents (from various departments) who work on the midnight shift. Do the following: 1. Create a group with all the traders on the midnight shift as members. You do not have to assign a manager. Call this group Midnight. 2. Create a profile with the Midnight group added as resource and select the Record All Calls on Members privilege. Call this profile Record Midnight. 3. Attach the Record Midnight profile to Steven. Note: This profile does not include privileges to PBO Requests - do these separately.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
37
What is a Group?
A manager of a subgroup is a considered regular group member of all higher level groups, (i.e., all members and managers of all subgroups appear in one flat layer).
EXAMPLE:
The following occurs: All members of Groups 2 and 3 become members of Group 1. Thus, Mary becomes a member of Group 1 (not a manager of Group 1). All members of Group 3 become members of Group 2. Thus, Mary becomes a manager over the members of Group 3. Mary does not inherit the managerial profiles from Group 3, only those from Group 2.
Includes a list of all the users who belong to the group. (Including all users in the groups subgroups.) Includes a list of all profiles attached to the group. Includes a list of all profiles attached to the groups managers.
To display a groups details: 1. In the Folders pane, expand the Groups folder and select a group.
The combined privileges from all selected profiles are shown in the Profile Privileges area.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
38
What is a Group?
Click Show Privileges Select one or more profiles Direct Profile Inherited Profile View results here
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
39
What is a Profile?
What is a Profile?
A profile is a set of privileges. You create profiles containing privileges to different parts of your system and/or to users within your system. By attaching a profile to a user or group, the user receives the privileges defined in the profile. Profiles attached to groups are inherited by all members of the group. See Rules of Profile Inheritance on page 40. Profiles should be created with job positions in mind. When the privileges of a profile are changed, the change automatically filters through to everyone in the system who has that profile. (Whether it was acquired directly or inherited.)
EXAMPLE:
The Compliance profile includes privileges for playing back interactions. The entire Compliance department has this profile. You add the privilege to create lists to the Compliance profile. The entire Compliance department now has the privilege to create lists. NICE Perform is packaged with several predefined profiles. You can use these profiles as is, modify them, or create your own. Predefined profiles are described in Defaults Provided with NICE Perform on page 43. Direct and inherited profiles can be identified by their icons:
Direct profile
Inherited profile
Profiles can only be removed at the level at which they were directly attached.
A profile attached on the profiles tab of a user definition is received by only that user and is directly acquired. A profile attached on the profiles tab of the group definition is received by all members of the group (including its managers) and its subgroups. This is called an inherited profile. It appears on the Groups profiles tab as directly attached. On the groups managers profiles tab and on each individual users profile tab, it appears as inherited.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
40
What is a Profile?
A profile attached on the managers profiles tab of the group definition is received by all direct managers of the group (not by the managers of its subgroups). It is an inherited profile and follows the rules of inherited profiles. See Rules for Inherited Profiles on page 41.
EXAMPLE:
Referring to the group structure shown below, the profile called Playback is attached on the Profiles tab of Group 2.
The results are as follows: Group 1 - does not inherit the Playback profile. Group 2 - all members and managers inherit the Playback profile. Group 3 - all members (this includes managers) inherit the Playback profile. The Playback profile appears with the direct profile icon only on the Profiles tab of Group 2. This is from where it can be removed. On all other profile tabs (groups, managers, and individual users) it appears with the inherited profile icon.
TIP: Attach all profiles (users and managers) at group level and not directly to users. This way, if users move between groups, or managers change, everyone will have the correct privileges. An exception to this rule would be if you need to maintain contact with a specific employee as might be the case with a new trainee program. Rules for Inherited Profiles
An inherited profile can only be removed at the level from which it was attached. If a user is removed from a group, all profiles inherited from that group are removed from the user. Profiles attached directly to the user, remain. A user who is added to a group as a group member, automatically inherits all profiles on the profiles tab of the group definition. This includes both inherited and directly attached profiles. A group member made into a manager of the group, automatically inherits all profiles on the managers profiles tab of the group definition. This includes profiles that the group inherited and profiles that were directly attached to the group.
EXAMPLE:
The Equities group has a profile called Playback. Agent Timothy, a new employee is added as a member to this group. Timothy automatically inherits the Playback profile.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
41
What is a Profile?
A list of all the profiles appears in the Contents pane and in the Details pane.
2. Double-click a profile.
3. To display privileges, in the Profiles Privileges area, expand a category and select an entry.
The number that appears in parenthesis next to each category name reflects how many entries appear for that category. The profile may or may not have privileges for each entry.
EXAMPLE:
Groups (2) shows that there are 2 groups in this category. Expand the Groups category and you will see Any Managed Group and All Users (even if they have no privileges selected). Add a group to the profile, assign some privileges to it, and save the profile. The category title becomes Groups (3).
TIP: If No Profile Assigned appears in the Profile Privileges title bar, the profile selected is empty and does not contain any privileges.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 42
into the database via the Total Recording System (in case of a CTI failure). These interactions lack CTI parameters, such as Agent Name and Number of Holds. These interactions are attributed to the default user called User Basic Recordings. To query or play back these interactions, the user will need permission to access the user called User Basic Recordings.
Superuser NICE - This user is defined as a system user and cannot be removed from your system. This user has one profile attached directly to it, the predefined profile called Superuser. Superuser cannot be removed from Superuser NICE. By default, its login name is nice and its login password is nice. The login password can be changed. A user logging into the system as
Superuser has complete access to the entire system and all its users. This user should only be used by the highest level administrator. In an Active Directory environment, when you log in with the Administrator user name, it is automatically linked to Superuser NICE.
User Unmapped - This User is defined as an agent (trader). Sometimes a technical failure occurs and interactions enter the database lacking basic information such as Extension or Agent ID. These interactions therefore cannot be attributed to an agent. Instead, they are attributed to the default user called User Unmapped. To query or playback these interactions, the user will need permission to access the user called User Unmapped. Default Profiles Superuser - Allocates complete privileges to the entire system and all its users. It is attached to Superuser NICE and cannot be removed. It can be attached to other users or groups in your
system. This profile should only be given to the highest level administrator. You cannot open the details view of Superuser, therefore it will not appear in the search results of a Quick Search. The predefined profile Administrator/IT is identical to the Superuser profile, however it can be modified if needed, to remove some privileges.
Administrator/IT - This profile is identical to the Superuser profile. However, it can be
Users.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
43
Basic Columns - A profile that includes view and query privileges to the most common data fields. It is attached to the All Users group. This means that all users in your organization tree will
have view (and some query) privileges to most data columns. You can remove this profile and attach it to a smaller group of system users. However, removing this profile might limit some functionality, such as evaluations, which requires access to transparent key data columns.
Compliance - The compliance officer approves requests for playback/tape. When approving a request, the compliance officer determines whether the trader will play back the interaction independently (a PIN code is sent to the trader) or whether the trader must listen to the interaction together with the compliance officer (in a conference call). NOTE:
The compliance officers approval in the compliance flow is optional and can be defined by assigning playback privileges. See Playback Workflow Privileges on page 132. Playback via conference is optional and can be defined via the general privileges for the site. A compliance officer receives an email notification each time a request awaiting compliance is generated by a user in one of the compliance officers groups or subgroups. This enables the compliance officer to focus on the requests that require his or her immediate attention. Depending on the defined compliance privileges, a compliance officer can view the list of incoming requests for the entire trading floor or for the officers groups and subgroups in the in the Incoming Requests tab.
The compliance officer can also extend a playback availability period, delete calls and play back interactions from his or her desktop.
Manager - The trading desk manager can initiate requests for playback/tape for any user in his or her groups and subgroups. In addition, the trading desk manager approves playback and tape requests for the traders in his or her groups and subgroups. After the trading desk manager approves a playback/tape request, the request is forwarded to the compliance officer. NOTE: The desk managers approval in the compliance flow is optional and can be defined by assigning playback privileges. See Playback Workflow Privileges on page 132. Trader - The trader can request playback and/or a tape. After the trader receives approval, the
trader can play back a call within a defined playback availability period. This role is intended for traders, trading floor staff and back office personnel.
Other Default Settings nice nice - nice is the login name and nice is the login password for Superuser NICE. The login password can be changed. In an Active Directory environment, use the Administrator Windows user name and password defined in the Active Directory. It is automatically linked to Superuser NICE.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
44
All Users - By default, the Basic Columns profile is automatically connected to the All Users
group. This means that all users in your organization tree will have view (and some query) privileges to most data columns. You can remove this profile from All Users and attach it to a smaller group of system users. However, removing this profile might limit some functionality which requires access to transparent key data columns.
Self - A special type of user. Anyone who receives a profile including privileges for Self, acquires these privileges for themselves only. Assign privileges to the Self user that you want to give many users for themselves. Attach this profile to a large group and all its users will acquire these privileges. Giving privileges to the Self user eliminates the need to create a separate profile for each user. EXAMPLE:
Create a profile called Record and playback myself. Include in it, for the Self user, privileges to view, query, play, record all calls, and record. Attach this profile to the All Users groups. Each agent who is also a system user in your organization will be able to play back and record their interactions if they have privileges to the relevant applications and interaction data fields. Users who are agents and not system users are unaffected by this profile. (Privileges to the interaction data fields are included in the predefined Basic Columns profile.)
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
45
Create profiles according to job position. Each profile should contain all the privileges necessary for one job position. Create a group for each job position. Add the users currently filling the job position to the group as members. Even if this means creating a group of one user. Attach profiles to groups and not directly to users.
By setting up profiles according to job positions, you make your organizational structure modular and easy to work with. Users changing job positions will automatically receive the profiles necessary for their new position. You will be working with job position titles instead of having to recall which employee is currently filling each position.
Login and Security options are set at the Organizational level. You can view and/or customize these settings at any time. See Customizing Organization Settings on page 105. NOTE:
Profiles, users, and groups are interrelated. You can work in any order that suits your needs. You will find that initially you will have to work back and forth to complete the cycle. The following workflow is provided as a guideline for getting started. Example: You can create all the users and then create groups adding the users to the groups as you create them, or, you might prefer to set up a shell of your organization by creating groups without users and then add the users to the groups as you add them to the system. NICE Perform provides the ability to import user databases. See About Imported User Databases on page 47 for more information.
To start working: 1. Create Profiles. Each profile contains a set of privileges. Create a profile for each job
Profile Privileges on page 62. You will have to work back and forth between the Groups and Profiles to complete the cycle.
6. Attach profiles to groups and to group managers. See Attaching Profiles to Users, Group
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
46
The hierarchy of imported groups cannot be changed in the Users Administrator. The drag-and-drop technique of moving groups around the Organization tree will not work. An imported group cannot be added as a subgroup to a manual group. A manual group can be added as a subgroup to an imported group. If an imported group is deleted, all of its subgroups are deleted, including any manually added subgroups. Imported user and group definitions can be edited manually. However, if another import process, with the users or groups definition, runs, the manual changes will be lost.
Chapter 2: Overview and Getting Started NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
47
3
Profiles
A profile is a set of privileges. You create profiles containing privileges to different parts of your system and/or to users within your system. By attaching a profile to a user or group, the user receives the privileges defined in the profile.
NOTE: NICE Perform has several predefined profiles. They are described in Defaults Provided with NICE Perform on page 43.
Contents
Guidelines for Creating and Attaching Profiles........................................................... 50 Before you Begin ............................................................................................................ 52 Creating a New Profile ................................................................................................... 54 Changing Profile Privileges ........................................................................................... 62 Attaching Profiles to Users, Group Members, or Group Managers........................... 66 Deleting a Profile ............................................................................................................ 69
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
49
Work with groups, not directly with users. Create a group for each job position and add users to groups. Even if a group has only one member. This allows you to work according to job positions and makes your system more modular. Attach profiles to groups and not directly to users. When adding users to a profile as a resource, add them as a group instead of directly. Use the following tips:
Tip Example
When you make changes to a profile, the change automatically filters through the system to all users who have this profile. This includes users who do not appear in your All Users list but are part of the system at a different level.
A management decision was made that all employees with access to the Users Administrator should be able to edit the system lists used on the Users Details tab. Edit the profile with privileges to the Users Administrator to include privileges to the Lists Editor (where system lists are created and maintained). All users who have this profile (directly or inherited) will automatically receive permission to use the Lists Editor. Tom has a profile that includes privileges to playback interactions from group A. Agnes is a new employee and is added as a member to group A. Tom now automatically gains privileges to playback Agnes interactions. Betty was in group A and moved to group B. Tom can no longer playback Bettys interactions. To view interactions for all agents in a group, you must have privileges that include: View and query privileges for the Group. Using query in the appropriate application. View and query privileges for the Interaction Data fields you want to view, such as Agent ID and interaction start and end times. (These are included in the predefined Basic Columns profile.)
If the profile includes a group as a resource, as users are added to or removed from the group, the profile automatically encompasses them. You must have access to data and users in order to see results in the applications.
The predefined profile, Basic Columns, gives most users access to the interaction data fields needed.
For a full description, see Defaults Provided with NICE Perform on page 43.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
50
Tip (Continued)
Example
You receive privileges to view agents from one profile, and privileges to playback interactions from another profile. You can then playback the agents interactions. Create a profile called Record and playback myself. Include in it, for the Self user, privileges to view, query, play, record all calls, and record. Attach this profile to the All Users groups. Each agent who is also a system user in your organization will be able to playback and record their interactions if they have privileges to the relevant applications and interaction data fields. Users who are agents and not system users are unaffected by this profile. (Privileges to the interaction data fields are included in the predefined Basic Columns profile.) Note: Without Self, you would need to create a profile with access to Tom and attach it to Tom, and one with access to Sue and attach it to Sue, etc. Using Self, you can create one profile and attach it to the persons who need privileges to themselves.
Agents and System Users do not automatically have privileges for their own interactions such as playback or record. They must be given privileges to use the applications and permission to view themselves. (Agent who will be playing back or recording their own calls must be defined as system users to be able to use the appropriate applications.) A special type of user, called Self, exists in your system. Anyone who receives a profile including privileges for Self, acquires these privileges for themselves only. Assign privileges to the Self user that you want to give many users for themselves. Attach this profile to a large group and all its users will acquire these privileges. Giving privileges to the Self user eliminates the need to create a separate profile for each user.
The Reporter Categories and Query Folders privileges have a unique option to assign privileges to All. A user having privileges to All, immediately acquires privileges to new Reporter Categories or Query Folders as they are added to your organization.
You have installed and are using User Administration Reports. You add Audio Analysis Reports to your organization. All users with privileges for the All Reporter Categories will automatically receive privileges for the Audio Analysis Reports. It is not necessary to add these privileges separately.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
51
This profile name appears in the Organization tree and is used to identify the profile. Give it a meaningful name. The users who will be managed by this profile.
Self - Any user who receives this profile, receives its privileges for themselves. Giving privileges to the Self user eliminates the need to create a separate profile for each user. EXAMPLE:
You want to give Agents John, Tom, and Sue privileges to play back their own interactions. Create a profile for Self with these privileges and create a group that includes John, Tom and Sue. When you attach the profile to the group, all agents in the group can play back their own interactions.
Groups
manager, all privileges apply to all groups managed by the manager. Thus, if a system user is a manager of two different groups and receives this privilege from one group, it will apply to the second group as well.
EXAMPLE:
Tom is a manager of group A and group B. The profile containing privileges to Any Managed Group is attached to the managers of group A. Tom now has the same privileges to group B. If his managerial status for group A is removed, he loses his privileges to group B.
All Users - Receive privileges over the all users group. Applications Interaction Data
The applications relevant to this profile and the specific privileges allowed for each application. The data fields from within the databases relevant to this profile and the privileges allowed for each.
TIP: The Basic Columns profile includes the most needed data fields. This profile is attached to All Users and is sufficient for most cases. For more information, see Defaults Provided with NICE Perform on page 43.
See the Interaction Data Reference Guide for an itemized description of the interaction data fields.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
52
Notes
The categories for the Reports to which privileges are required. The following special option is available:
All - Privileges are automatically applied to all current Reporter categories and to all new Reporter categories whenever they are added.
Query Folders
The Query folders that will be managed and accessible by this profile. The following special option is available:
All - Privileges are automatically applied to all current Query folders and to all new Query folders whenever they are added.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
53
In the Folders pane, click the New dropdown arrow and select New Profile. The New Profile wizard starts.
2.
3.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
54
Add Resource
4.
You can add privileges to Users, Groups, applications, data fields, Reporter Categories, and/or Query Folders now, or save the profile and add privileges later. Proceed as follows (do as many of the following steps as necessary):
To add privileges for Users or Groups, complete Step 5 on page 56. To add privileges for Applications, complete Step 6 on page 57. To add privileges for Reporter Categories, complete Step 7 on page 57. To add privileges for Query Folders, complete Step 8 on page 58. If necessary, add privileges for Business Data. See Assigning Privileges for Business
Data Fields on page 60.
To save the profile and add privileges later, proceed to Step 9 on page 59.
NOTE: NICE Perform includes a predefined profile called Basic Columns. The Basic Columns profile contains privileges to the most used data fields. This profile is sufficient for most uses. For more information, see Defaults Provided with NICE Perform on page 43. You attach it to users/groups in a separate procedure. If privileges to additional columns are required, see Changing Profile Privileges on page 62.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
55
5.
b. Expand the All Users or Groups folder and move users or groups to the Available Items list and then to the Select Items list. Then click OK to close the window.
c. One at a time, select each user or group and select the relevant privileges. For a
description of each privilege, see User Privileges on page 128 and Group Privileges on page 130. Users/groups for whom you do not select privileges, will not be saved with the profile!
d. After you select privileges for all users or groups, click Next to close the window.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
56
6.
c. Select the required privileges. (For a description of each privilege, see Applications
Add privileges for all Reports Categories - Select All and select privileges. These
privileges are automatically applied to all current Reporter categories and to all new Reporter categories whenever they are added. You do not need to add more Reporter Categories.
-or-
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
57
b. In the Available Categories list, select report categories and move them to the area on the right. Then click OK.
Select privileges for each Reporter Category before you click Next
c. One at a time, select each reporter category and select privileges. d. After you select privileges for all reporter categories, click Next to close the window.
Reporter categories for which you do not select privileges, will not be saved with the profile!
8.
Add privileges for all Query Folders - Select All and select privileges. These privileges
are automatically applied to all current Query folders and to all new Query folders whenever they are added. You do not need to add more Query folders.
-or-
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
58
b. In the Resource Tree list, select Query Folders and move them to the Selected Items list on the right. Then click OK.
Select privileges for each Query Folder before you click Next
c. One at a time, select each query folder and select privileges. d. After you select privileges for all query folders, click Next to close the window. Query
Folders for which you do not select privileges, will not be saved with the profile!
9.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
59
10. Click Finish. The profile is added to the system and appears in the details pane. You can now
attach this profile to groups or users. See Attaching Profiles to Users, Group Members, or Group Managers on page 66.
Profile name appears here
Business Data Business data fields are data fields that are available from your company site, such as customer
name and phone number. These are custom fields that differ for each organization. You must provide users with privileges to access them. They must be selected and defined by your site administrator using the System Administrator application in conjunction with the switch technicians. Once business data fields are defined for your site, you use the Users Administrator application to provide the relevant users with permission to access the business data fields.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
60
Determine which business data fields were defined by your site administrator. Create a profile which includes privileges to the business data fields in the Interaction Data area. See Creating a New Profile on page 54. Attach the new profile to the relevant users. Attaching Profiles to Users, Group Members, or Group Managers on page 66.
NOTE: In the relevant applications, display/access data as necessary. Example: In the Business Analyzer, use the Preferences window to display new fields.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
61
Open the Profile details. See Displaying Profile Privileges on page 42.
2.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
62
b. Expand the All Users or Groups folder and move users or groups to the Available Items list and then to the Select Items list. Then click OK to close the window.
c. One at a time, select each user or group and select the relevant privileges. (For a
description of each privilege, see User Privileges on page 128 and Group Privileges on page 130.) Users/groups for whom you do not select privileges, will not be saved with the profile!
d. After you have added privileges for all users or groups, click Save
. Users/groups for
whom you do not select privileges, will not be saved with the profile!
3.
b. In the expanded Applications list, click an application. The applications privileges appear in the Privileges for section.
c. Select the required privileges. (For a description of each privilege, see Applications
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
63
b. One at a time, select each data item and select the relevant privileges. For a description of
b. In the Available Categories list, select report categories and move them to the area on the right. Then click OK.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
64
Select privileges for each data item before you click Next
c. One at a time, select each reporter category and select privileges. Reporter categories for
which you do not select privileges, will not be saved with the profile!
d. After you select privileges for all reporter categories, click Save
. Reporter categories for which you do not select privileges, will not be saved with the profile!
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
65
Your organization is expanding. You will now have two groups of agents instead of one. You want to create a second group of agents with identical privileges as the original group. Select the Copy from other groups option, then select the profiles you want to copy. Profiles are attached using the Attach Profile wizard. The Attach Profile wizard starts automatically from within the New Group wizard, or you can start the Attach Profile wizard by clicking in one of the following places:
Group details: Profiles tab. Attach profiles to all of a groups members. Group details: Managers Profiles tab. Attach profiles to all of a groups managers. User details: Profiles tab. Attach profiles directly to a single user. (This should be the
NOTE: If you are attaching profiles from within the New Group wizard, you do not do this step. The title bar of the wizard will be Set Members Profiles or Set Managers Profiles instead of Attach Profile. All three wizards are identical and you use the following procedure.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
66
2.
Click Next.
3.
Select Select from the list of profiles , or Copy from other groups. Then click Next and continue according to your selection.
NOTE: When you copy from another group, all of the other groups profiles are listed. You can select to use some, or all of them.
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
67
a.
In the Available Profiles list, select one or more profiles. The privileges for the combined Profiles are displayed in the Profiles Privileges area. Click Next. A Summary of the selected profiles appears.
a.
In the Available Groups list, expand the Groups list and select a group. The Groups profiles are listed in the
Profiles attached to the selected group list. (If you are attaching profiles
b.
to a groups members, the groups members profiles appear. If you are attaching profiles to a groups managers, the groups managers profiles appear.)
b.
Select one or more profiles. Then click Next. A Summary of the selected profiles appears.
c.
Click Finish.
c.
Click Finish.
The profiles are attached to the user/group/managers. All copied profiles are directly attached to the group to which they are attached. (Including those that were inherited by the group they were copied from.) Profiles that are attached to group members (on the Profiles tab) are automatically inherited by the groups managers (on the Managers Profiles tab).
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
68
Deleting a Profile
Deleting a Profile
When a profile is deleted from the system, all users who have this profile immediately lose its privileges. A user who is logged in to an application will not able to continue in the application.
To delete a profile: 1. 2. 3.
In the Folders pane, click Profiles. In the Details pane, select the profile and click Delete Profile. Click Save .
Chapter 3: Profiles NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
69
4
Users - Agents, Traders, and System Users
IMPORTANT In the NICE Perform system, all Traders are Agents!
All users recognized by the system, regardless of their status, must be added to the NICE Perform system. This includes Agents (Traders) whose interactions are being recorded, managers and supervisors using the applications (known as System Users), and maintenance personnel (add them as system users with limited access to other resources).
NOTE: An agent (trader) in your system might never use any applications, or even be aware that NICE Perform is functioning, but must be added to the NICE Perform system in order to be recognized when recorded.
Contents
Before you Begin ............................................................................................................ 72 Adding a New User ......................................................................................................... 73 Displaying User Details.................................................................................................. 80 Customizing a System User .......................................................................................... 80 Changing Login Name and Password........................................................................ 81 Changing Login Name and Password (Active Directory) ........................................... 85 Changing Password Expiration Period....................................................................... 86 Deactivating or Reactivating a Login ID ..................................................................... 88 Deactivating or Reactivating a Login ID (Active Directory) ........................................ 89 Attaching Profiles to System Users and Displaying Privileges................................... 89 Adding an Agent Identity (First-Time and Multiple) ....................................................91 Deleting a User Definition ..............................................................................................92 Showing/Hiding Deleted Users .................................................................................. 93
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
71
Before you start the New User wizard, have the following information ready:
Item Notes First, Middle, and Last names Email Address Is this user a system user? * Is this user an agent? * Middle name is optional Optional Have ready: Unique NICE Perform Login ID and password for logging in to NICE Perform applications Have ready: Unique Windows user ID, Site Location, Switch ID, and unique Agent Ids) (free-seating) or unique Extension (fixed-seating). See Which Agent Identification Should I Use? Agent ID vs. Extension on page 33.
* Each user must be identified as either a system user, an agent, or both. This status can be changed at any time. Agents who will view their own evaluations must be defined as system users.
IMPORTANT In environments where screen recording is performed at more than one branch, to avoid duplicate users in the system, you must define the Agent Identification for Screen Recording value. This value must be unique for each branch at your site. For more information, see the NiceScreen Installation Guide: Branch Site Support.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
72
In the Folders pane, click the New dropdown arrow and select New User. The Create New User wizard starts.
NICE Perform authentication environment
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
73
2.
Click
In the Active Directory environment, these values must match the Windows User Name and Domain defined in your Active Directory
3.
4.
Click
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
74
5.
NOTE: Values for all dropdown lists are created using the Lists Editor application.
6.
Select Agent, System User, or both. (Traders must be defined as Agents!) Then click .
If you selected Agent, the Agent Details window appears. Continue with Step 7. If you selected System User, proceed to Step 8. If you selected both, the Agent Details window appears first. Continue with Step 7.
7.
To define an Agent, you must define at least one Agent Identity. Do the following:
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
75
a. Agent identification for screen recording: If you need to record this agents screens,
and your site is comprised of multiple branches, enter a unique name representing the branch at which this agent resides. For more information, see NiceScreen Installation Guide: Branch Site Support.
NOTE: If your site is not comprised of multiple branches or if you do not need to record this agents screens, your can leave this field blank or supply an agent identification for future use. b. Each agent must have at least one Agent Identity. For a description of agent identities,
see Which Agent Identification Should I Use? Agent ID vs. Extension on page 33. For each agent identity you are defining, click . The Agent Identity window appears.
c. Select a switch. The Site name automatically appears. d. Enter the Agent ID or Extension and click
NOTE: The agent ID can only contain up to 32 characters. e. When all Agent Identities have been added, in the Agent Details window, click
f. If you are not defining a System User, the Summary window appears. Proceed to Step 11. 8.
To define a System User, define a user login. Then select to attach profiles now or later.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
76
To define a System User, enter a unique Login Name and Password (twice). This login name and password will be used by the user to access NICE Perform applications.
Click
10. Profiles should be attached at group level, according to job position. This is done after this
wizard is complete and groups are defined. See Attaching Profiles to Group Members and Group Managers on page 104. However, if you must attach a profile directly to a System User, you can do so now. Select profiles for the user and click .
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
77
The new user definition is created and appears in the details pane.
User name appears here
Add the user to an existing group. See Adding Group Members on page 100.
Chapter 4: Users - Agents, Traders, and System Users 78
Create a new group. See Groups on page 95. Create a new profile. See Profiles on page 49. In a NICE Perform authentication environment, you can set individual password and login options. See Changing Login Name and Password on page 81. In an Active Directory authentication environment, all password policies are handled by the Active Directory. To make changes, use the Active Directory Management Console.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
79
Display a users details by double-clicking the username in any of the lists in which it appears. For information about user details, see User Details and Profiles on page 34.
2.
TIP: To refresh the Contents pane after editing a username: In the Folders pane, click the group level of the user. The Contents pane refreshes.
System Users are users who log in to NICE Perform applications. As a supervisor with privileges to edit the user, you can edit the following for each individual System User at any time:
In a NICE Perform authentication environment
The login name and password used by the System User to log in to NICE Perform applications. See Changing Login Name and Password on page 81.
Password Expiration - How often the System Users must change their password. This is set at the Organization level. If you define it individually for a System User, these settings take precedence over the organization settings. See Changing Password Expiration Period on page 86.
Temporarily deactivate a System Users login name or reactivate one that has been automatically deactivated due to either invalid password entry or inactivity. See Deactivating or Reactivating a Login ID on page 88.
Attach profiles directly to the System User. This is the same for all authentication environments. See Attaching Profiles to System Users and Displaying Privileges on page 89.
The login name and password used by the System User to log in to NICE Perform applications. See Changing Login Name and Password (Active Directory) on page 85.
Password Expiration - How often the System User must change their password. Password policy is determined by the Active Directory. To change password policy, use the Active Directory Management Console.
Temporarily deactivate a System Users login name or reactivate one that has been deactivated. See Deactivating or Reactivating a Login ID (Active Directory) on page 89.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
80
Attach profiles directly to the System User. This is the same for all authentication
environments. See Attaching Profiles to System Users and Displaying Privileges on page 89.
The password that a system user uses to log in to the NICE Perform applications can be changed either by the user, or a manager with privileges to edit the users details.
Changing someone elses password
Managers who have access to the Users Administrator application and privileges to edit the system users details, can change a system users login password from within the Users Administrator application in one of the following ways:
Manually - the manager accesses the users details and types a new password. Using this
method, the manager knows the system users password and must relay it to the user. See Manually Resetting Someone elses Login Password and Name on page 82.
Automatically - the manager accesses a group list where the user is a member (or the All Users group) and requests the system to send a system-generated password directly to the users email address. The user must have a valid email address on an email server configured in the system. The manager does not receive a copy of the new password. If the user wants to choose a password, the user can log in to NICE Perform using the new password and manually change the password. See Automatically Resetting Someone elses Login Password on page 83.
System users can change their own passwords. They do not need access to the Users Administrator application to change their own password. System users can change their own password in the following ways:
Manually - the system user can choose his/her own password by manually changing it after
logging in to the NICE Perform applications. See Manually Resetting your own Login Password on page 83.
Automatically - the system user does not have to be logged in to the NICE Perform
applications to use this method. This method is intended for users who forgot their passwords. Using this method, the system user receives a system-generated password by email. The system user must know their own login name to receive a new password by email. If a system
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 81
user wants to choose a password, it can be edited manually after logging in to the system using the system-generated password. See Automatically Resetting your own Login Password on page 84.
IMPORTANT If the system users email address is incorrect or the email server is incorrectly configured in the system, an email with a new password will not reach the user, however the system users password will be changed in the system. In this case, a manager must enter the system and manually redefine a password for the system user as described in Manually Resetting Someone elses Login Password and Name on page 82.
In the Users Administrator application, display the user details. See Displaying User Details on page 80. Click the System User tab.
3. 4.
Enter the new Login Name and/or Password (twice) and click Save Relay the new information to the system user.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
82
In the Users Administrator application, display a group or the All Users group.
2.
Select one or more users from the list and click Reset Password. New passwords will be sent by email to all the selected users.
Log in to NICE Perform applications suite using your system user login name and password.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
83
2.
3.
Complete the window and click OK. The next time you log in to NICE Perform, use the new password.
Manually Resetting Someone elses Login Password and Name on page 82 Automatically Resetting Someone elses Login Password on page 83
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
84
2.
Enter your Login Name and click Reset Password. A new password will be sent to your email address. If your email address is incorrect or the email server is incorrectly configured in the system, an email with a new password will not reach you, however your password will be changed in the system. In this case, a manager must enter the system and manually redefine your password.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
85
In an Active Directory authentication environment, system user login name and password are controlled solely by the Active Directory. Each system user has a unique Windows User Name/Domain identification. To change the system users identification or password you have to do it in two places; in the Active Directory, and in the Users Administrator.
TIP: To temporarily deactivate a system user, change their Windows User Name to one that is not defined in the Active Directory. The new definition will be saved but the user will not receive authentication to log in to NICE Perform.
Use the Active Directory Management Console to change the users Windows User Name, Domain, and/or Password. In the Users Administrator, display the user details. See Displaying User Details on page 80. In the General tab, edit the Windows User Name and/or Domain to match the new Windows User Name/Domain defined in the Active Directory.
4.
Click Save
Password restrictions and options are set at organizational level. You can change the password expiration period for each individual user or require a new password at next log in (use this option for new users). Password options set at user level take precedence over the organization settings.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
86
Password options are set at organizational level. See Defining Password Policy for System Users on page 106.
To change the password expiration date: 1. 2.
Display the user details. See Displaying User Details on page 80. Click the System User tab.
3.
To make the password to automatically expire after a specified number of days, select Expires in ____ days and select the number of days. The next time the user logs in, a new password must be entered.
4. 5. 6.
To prevent the user from changing their own password, select User cannot change
password.
To force a user to change passwords the next time they log in, select User must change
password at next login. (Use this option for new users.)
Click Save
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
87
System User Login IDs are automatically deactivated in the following instances:
The user attempts to log in with an invalid password more than the allowed number of times. The user does not log in for more than a specified number of days.
Limits for both of these conditions are set at organizational level. See Defining Security for NICE Perform Applications on page 110. When one of the limits is reached, the system users login ID is disabled.
To deactivate or reactivate a System User login ID: 1. 2.
Open the users details for editing. See Displaying User Details on page 80. Click the System User tab.
3.
In the Accounts Options area, clear the Login ID is enabled checkbox to deactivate the login ID
-or-
Click Save
.
Chapter 4: Users - Agents, Traders, and System Users 88
In an Active Directory authentication environment, system user login name and password are controlled solely by the Active Directory. Each system user has a unique Windows User Name/Domain identification. Password policies are managed by the Active Directory.
To deactivate or reactivate a System User login ID: 1. 2.
Open the users details for editing. See Displaying User Details on page 80. In the General tab, edit the Windows User Name and/or Domain as follows:
To deactivate a system user, temporarily change the Windows User Name to one not
defined in the Active Directory.
To activate a system user, edit the Windows User Name and Domain to be identical to
those defined in the Active Directory.
3.
Click Save
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
89
Each System User can have more than one profile (direct or inherited). Profiles work in combination. You can view the privileges of one or more profiles together to determine if the attached profiles in combination achieve the required privileges. The status of each profile (direct or inherited) can be determined by the icon in the profile type column as follows: Profile attached directly to the user. Profile attached to a group of which the user is a member and so is inherited by the user.
Open the users details for editing. See Displaying User Details on page 80. Click the Profiles tab.
3.
Select one or more profiles from the Profiles list. (Use the Shift or Ctrl keys to multi-select profiles.) Then click . The combined privileges from all selected profiles are displayed in the Profile Privileges area. Attach more or remove unnecessary profiles.
Click Attach Profiles and follow the directions for Attaching Profiles to Users, Group Members, or Group Managers on page 66. Click Save .
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
90
Open the users details for editing. See Displaying User Details on page 80. Click the Agent tab.
For multi-branch sites configured to perform screen recording define a value that represents the branch at which this agent is located
In environments where more than one branch is recording agents screens, to avoid duplicate users, enter a value in the Agent identification for screen recording field. This value must be unique. It represents one branch at your site. For more information, see the NiceScreen Installation Guide:Branch Site Support.
3.
Click
4. 5.
Select a switch. The Site name automatically appears. Enter the Agent ID or Extension and click OK.
NOTE: The agent ID can only contain up to 32 characters.
6. 7.
To add more than one Agent Identity, repeat from Step 3. Click Save .
Chapter 4: Users - Agents, Traders, and System Users 91
An agent/system user leaves the organization permanently. Delete the user definition following the procedure found in this section. Review Guidelines for Deleted Users found below before continuing. An employee takes an extended leave of absence with plans to return. Remove the employees agent and system user status, leaving the user definition available for use upon the employees return. Do not delete this user! Instead, do the following:
a. In the users System User tab, select the active checkbox and then deactivate their login
ID. This deactivates the System User status while keeping the user definition. See Deactivating or Reactivating a Login ID on page 88.
b. On the users Agent tab, clear the active checkbox. NOTE: You cannot clear the agent checkbox until after the user is defined as a system user. There cannot be an inactive agent in the system, however there can be an inactive system user in the system. Guidelines for Deleted Users
Deleted users cannot be reinstated at any time. Deleted users remain in the system as a ghost. They can be used as search criteria in queries. You can playback interactions that belong to a deleted agent. The icon for a deleted user is . This is regardless of their previous status.
Deleted users cannot be added to a group or as a resource to a profile. The show/hide option is set separately for each application, within the application itself. In the Users Administrator, you define the period of time during which deleted users are displayed. See Showing/Hiding Deleted Users on page 93. Details of deleted users cannot be edited. If a deleted user was an agent, all recorded interactions remain in the system. A deleted users agent identity can be assigned to a different user.
IMPORTANT Deleted users cannot be reinstated at any time! If you will want to reactivate the user at a later date, deactivate the users Agent status and the users System User login ID. See Deactivating or Reactivating a Login ID on page 88.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 92
Review Guidelines for Deleted Users on page 92 before continuing. In the Folders pane, select All Users.
TIP: Before deleting a user, you can view the users details, confirming that you are deleting the correct user. In the Group Members list, double-click the user to display the users details. Once you have determined that the user is the one you are seeking, click return the All Users view and proceed with Step 3. to
3. 4.
In the Details pane, select a user and click Click Save . The user is deleted from the Organization.
Betty is deleted from the Organization on January 1. The retention period for All applications is 3 months. For Reporter it is 12 months. In applications where Show Deleted Users is selected, Betty will appear in the Users list until March 31. In the Reporter, Betty will appear until December 31. For Betty to appear in April, change the Retention period for All applications to 4 months.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
93
Select Organization and then click the Settings tab. Expand the Display section.
Expand
2.
To show deleted users in the Users Administrator, select the Show deleted users details in Users Administrator checkbox.
-or-
To hide deleted users in the Users Administrator, clear the Show deleted users details in Users Administrator checkbox.
3.
User records will never be deleted from the User database, even after this retention period. The maximum value for retention period is 99 months.
4. 5.
Click . All deleted users will be shown/hidden in all areas of the Users Administrator application as indicated. In other applications, select the Show Deleted Users checkbox to display the users deleted within the retention period.
Chapter 4: Users - Agents, Traders, and System Users NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
94
5
Groups
A Group is a collection of users united for the purpose of attaching the same profiles to all the users, and to allow them to be managed by the same manager(s). Groups are generally created according to job positions and work groups. You can group agents (traders) together who do not need access to any parts of the system to allow easy access for a higher-level manager. In this case, you would create a group of agents without any profiles attached and then you can add this group as a resource to a profile which will be attached to a manager. A manager of a group does not gain automatic privileges over the groups members. A profile must be created with access to the group, and View, Edit, and Playback privileges. This profile must be attached to the groups manager(s). When creating a profile for managers, use Any Managed Group instead of directly attaching groups. This way, managers always have privileges to the groups they manage. Groups, once created, can be moved around the organization tree using drag-and-drop technique.
EXAMPLE:
Create a profile called Manager. For Any Managed Group, select View, Edit, and Query. Attach this profile on the managers profiles tab to give the manager privileges over the groups members.
Contents
Before you Begin ............................................................................................................ 96 Creating a New Group .................................................................................................... 97 Adding Group Members...............................................................................................100 Removing Group Members ......................................................................................100 Defining a Group Manager...........................................................................................102 Attaching Profiles to Group Members and Group Managers ...................................104 Deleting a Group...........................................................................................................104
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 95
Profiles attached to a group and received by a user are called inherited by the user. Inherited profiles can be removed only at the level at which they were attached (i.e., group level). If a user leaves a group, all inherited profiles are automatically removed. If a user joins a group as a member, the new user automatically inherits all of the groups profiles. If a members status within a group changes to manager, the member automatically inherits all profiles attached to the groups managers. Profiles attached to group members are inherited by the groups managers and appear on the groups Managers Profiles tab. A user retains manager status only at the level it was assigned.
Before you start the New Group wizard, have the following information ready:
Item Notes Group name and description Users to add as Members of the new group Profiles The group name appears in the Organization tree. Create meaningful group names for easy identification. Group managers must first be added as group members. You give them managerial status in the Group Details window. If the profiles are not yet created, they can be attached to the user at a later time.
Groups can be moved around in the groups tree using the drag-and-drop technique (Groups cannot be moved into one of their own lower-level sub-groups).
IMPORTANT Groups created using the Importer cannot be moved around in the groups tree using the drag-and-drop technique.
Group members become members in all higher-level groups. Group managers become members in all higher-level groups. (Manager status is only retained for the group where it was directly assigned.) Profiles are inherited as described in Rules of Profile Inheritance on page 40.
Chapter 5: Groups 96
In the Folders pane, select the parent group for the new group and click New.
2.
3.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
97
The group name appears in the Organization tree. Create logical group names for easy identification.
4.
5.
You can STOP here and attach profiles later: Click Finish and proceed to Step 6.
-or-
You can continue with the wizard to attach profiles to group members: In the Profiles area, select the appropriate checkboxes and then click Finish. Continue with Attaching Profiles to Users, Group Members, or Group Managers on page 66.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 98
The group is added to the system and appears in the details pane.
Group name appears here
6. 7.
To assign a group manager, continue with Defining a Group Manager on page 102. To attach profiles, see Attaching Profiles to Users, Group Members, or Group Managers on page 66.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
99
Search for the user and then drag and drop the user into the group. See Adding a User from the Search Results to a Group on page 20. Open the Group details and add members, as described is the following procedure.
Display the groups details and click the General tab. Click .
3.
4.
To assign a group manager, continue with Defining a Group Manager on page 102. Attach an existing profile to the group: Continue with Attaching Profiles to Users, Group Members, or Group Managers on page 66. Add the group as a resource to a profile: Continue with Profiles on page 49.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
100
Organization tree. When you remove a user from a group, the user is also automatically removed from all higher level groups, and lower level groups, down to the level at which they were directly added.
EXAMPLE:
Using the group structure shown below, Betty is added as a member to Group 3. Betty automatically becomes a member in Group 1 and in Group 2.
Betty is removed from Group 2. Betty is automatically removed from Groups 1 and 3 as well. Removing a member from a group does not delete the user from the All Users list. You can add the user as a member to a different group. Users who were deleted from the Organization can be removed from a group. However, deleted users cannot be added to a group.
To remove a member from a group: 1.
Open the group details and display the General tab in a group where the user is a member.
Remove
TIP: Before removing a user from a group, you can view the users details, confirming that you are removing the correct user. In the Group Members list, double-click the user to display the users details. Once you have determined that the user is the one you are seeking, click return the groups details view and proceed with Step 2. 2. 3. to
The following occurs: Mary is automatically a member of Group 1. Mary is a manager of Group 2 only. Mary is not a manager of Group 1.
In the Folders pane, select a group to display its details. In the General tab, in the Group Members list, select a system user and click Set as Group Manager. Click Save . The user icon changes to include a red asterisk:
NOTE: All profiles listed in the Managers Profiles tab are automatically inherited by the new manager. Inherited profiles can be identified by their icon:
4.
Verify that the manager has a profile containing the appropriate privileges in one of the following places:
c. Verify that the appropriate privileges in the Privilege for section are selected.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
102
-or-
The user might have received profiles by being a member or manager of another group. If
one of these profiles has privileges for Any Managed Group, the user will have these privileges over the members of the current group as well. To verify if the user has privileges for Any Managed Group from any profile:
a. Open the user definition and click the Profiles tab. (You can double-click the user
c. In the Resources list, expand Groups and select Any Managed Group.
The manager will have all of the privileges that are selected for Any Managed Groups over the members of the current group and over the members of all the groups for which he/she is a manager.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
103
Show the Groups details. Click either the Profiles or Managers Profiles tab. Start the Attach Profile wizard: Click .
Continue with Attaching Profiles to Users, Group Members, or Group Managers on page 66.
Deleting a Group
To delete a group from the Organization tree:
In the Folders pane, select the group in the Organization tree and click Delete
The selected group is deleted from the organization. It is automatically removed from all profiles. Its users are not deleted from the All Users group or from other groups. Members that originated in the deleted group are removed from all higher-level groups.
Chapter 5: Groups NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
104
A
Customizing Organization Settings
There are several parameters that can be set at the organizational level. These parameters affect all users and all groups defined in your system. Some affect other applications in your system. All the parameters have default settings which you can keep or customize to suit your needs. You can modify the parameters at any time. Your system will be affected from that time onwards. All changes will not affect system users currently logged in to NICE Perform. They will only be affected the next time they log in.
Contents
Defining Password Policy for System Users .............................................................106 Password Policy Options .........................................................................................107 Defining Security for NICE Perform Applications ..................................................... 110 Login Details ............................................................................................................ 111 Security Options....................................................................................................... 112 Defining Target Number of Evaluations ..................................................................... 113 Defining the Domain Display ....................................................................................... 116
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
105
This procedure is not relevant in an Active Directory authentication environment. In the Active Directory authentication environment, system user password policies are determined by the Active Directory. The Passwords tab is hidden. To change password policy, use the Active Directory Management Console. See How are System Users Authenticated? NICE Perform vs. Active Directory on page 32.
Changes go into effect at each new Login. Users currently logged into NICE Perform applications are not affected by the changes.
Password policy is set at the organizational level. These settings apply only to system users logging in to NICE Perform applications, not to agents. Agent password policy is determined by their individual operating systems. Following are password restrictions that cannot be overridden.
Password expiration period. Forcing a new system user to change passwords at next login.
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
106
In the Folders pane click Organization. Then click the Security tab.
2. 3.
Define the password options as needed. See the values in Password Policy Options on page 107. Click Save .
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
107
In an Active Directory authentication environment, password policy is defined in the Active Directory.
These options can be changed at user level. See Changing Password Expiration Period on page 86.
Password never expires - Passwords are valid forever. Expires in _ days - Passwords automatically expire after specified amount of time. The next time a system user logs in, they must enter a new password.
Change anytime - System users can change their own password at any time. Allow change after _ days - System users can change their own password only after the
specified amount of time has passed. This option can be changed at user level. See Changing Password Expiration Period on page 86.
User cannot change password - System users cannot change their own password. Selecting this option disables the Change password at next login option in the New User Password section.
Change password at next login - Requires each system user to enter a new password the first time they log in to the system. This option can be changed at user level. See Changing Password Expiration Period on page 86.
Appendix A: Customizing Organization Settings 108
Password History
Do not save password history - Allows system users to use previous passwords. Remember last _ passwords - Forbids system users from reusing the specified number of
past passwords.
Password Checking
At least _ characters - Specify a minimum length for each password. Must be greater than
or equal to 5.
Strict password checking - Eliminates the use of certain passwords as follows:
No leading or trailing blanks. No more than 2 identical consecutive characters. Example: abbba Cannot contain only digits or only letters. Example: 12345, abcde
Forbidden Passwords
Use this area to add a list of passwords that may not be used by any system user. Example: secret a1b2c3
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
109
Security options allow you to limit invalid entries and access to NICE Perform applications even when a valid password is known. They are set at the organizational level. These settings apply to system users logging into NICE Perform applications, not to agents. Agent security is determined by their individual operating systems. System users can see details from their last login as well as any failed attempts to login to their account.
Deactivating/reactivating a login account can be overridden for each individual user as needed. See Deactivating or Reactivating a Login ID on page 88.
To define Security Options: 1.
In the Folders pane click Organization. Then click the Security tab.
NICE Perform Authentication environment
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
110
2. 3.
Define security options as needed. See the values in Security Options on page 112. Click Save . Changes go into effect at each new Login. Users already logged into NICE Perform are not affected by the changes.
Login Details
This section explains some of the options available in the Settings section for the Organization. You can choose to show the details from the last time that a user logged in to the NICE Perform Applications Suite. These details appear for the user to see at the time that he/she logs in.
In an Active Directory authentication environment, this option only applies if single sign-on is not implemented. (i.e., The user is not automatically logged in to NICE Perform after logging in to Windows. The user has to re-enter their login name and password in the NICE Perform login window.)
To display last login information: 1.
Select Organization and then click the Security tab. Expand the Security Options section.
Expand
2. 3.
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
111
Security Options
This section explains the security options for the Organization. For instructions on changing security options, see Defining Security for NICE Perform Applications on page 110.
NICE Perform Authentication environment
Accounts
This section is not available in an Active Directory authentication environment, where login accounts are handled by the Active Directory.
will become disabled after the specified number of invalid login attempts. To reactivate the account, edit the user, then click the System User tab and in the Account Options area, select the Login ID is enabled checkbox. Login IDs can be deactivated manually for each user. See Deactivating or Reactivating a Login ID on page 88.
Deactivate Login ID after _ days of inactivity - The system users account will become
disabled if no login attempts were made for the specified number of days. To reactivate the account, edit the user, then click the System User tab and in the Account Options area, select the Login ID is enabled checkbox. Login IDs can be deactivated manually for each user. See Deactivating or Reactivating a Login ID on page 88.
Auto-lock
Auto-lock after _ idle minutes - If no activity is detected for the specified amount of time, the login window automatically reappears and the system user has to reenter the password. The application does not automatically close.
Appendix A: Customizing Organization Settings 112
Define that 4 is the target number of evaluations that is required to be performed on any agent in the organization within 30 days.
-or-
define a target number of evaluations based on the seniority of each agent. When defining by seniority, you must define at least one seniority period and a corresponding target number of evaluations for that period; and you must define another target number of evaluations for those agents above the designated time period. You can also define two additional time periods bringing the total to four periods.
EXAMPLE:
You can define the following: An agent who is less than 1 month in the organization will have a target number of 10 evaluations within 30 days. An agent who is in the organization more than 1 month, but less than 3 months, will have a target number of 8 evaluations within 30 days. An agent who is in the organization more than 3 months, but less than 8 months, will have a target number of 5 evaluations within 30 days. An agent who is in the organization more than 8 months will have a target number of 2 evaluations within 30 days.
In the Folders pane, click Organization. Then click the Settings tab.
Appendix A: Customizing Organization Settings 113
2.
Expand
NOTE: If you do not want to assign a target number of evaluations for agents, select None. 3. 4.
Select Agent Evaluation Target. Select a target period from the Target Period (in days) drop-down menu. This is the time-frame in which the number of evaluations defined must be performed. For example, if you select 30 days, then the number of evaluations defined must be performed within 30 days.
5.
Select the number of evaluations from the Default Target Evaluations drop-down list.
NOTE: The default number you define here is used when:
6. 7.
You do not choose to define target evaluations based on seniority. -orYou choose to define the target number of evaluations based on seniority, but an agent does not have a hire date defined in the system.
If you are not defining seniority, proceed to Step 8 on page 115. To define a target number of evaluations based on agent seniority, do the following:
a. Select Define by seniority. b. (Mandatory) In the first row, select the timeframe and target evaluation number for the
period, select the checkbox and define the timeframe and target.
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 114
d. ((Mandatory) In the More row (fourth row), define a target number of evaluations to be
applied to any agent whose seniority is above the defined periods. See Example: on page 113.
8.
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
115
When your Web Applications server is connected to the Microsoft Windows Active Directory authentication environment, all domains defined at the site are displayed in the Domain tab. When you click the Auto Detection button, Users Administrator queries System Administrator for the domains, then System Administrator interfaces with the Active Directory and sends Users Administrator a list of the domains defined at the site. In this environment, each user is associated to a domain. You can choose to associate NICE Perform users with either the NetBIOS name or the DNS name. When you define a new user, your selection (NetBIOS or DNS) is displayed in the users Details in the Domain dropdown selection list.
In the Folders pane, select Organization. Click the Domains tab. If the Domains tab opens blank, click .
Users Administrator queries System Administrator for all the domains defined at the site. The domains are displayed in the Details pane.
3.
To the select the Domain type you want to associate with each user, in the Settings > Display Domain Name Properties area, select NetBIOS Name or DNS Name. Your selection is reflected in the General tab for each user, and in the Create New User wizard. To remove a domain from the dropdown list, select it in this list and click Delete.
4.
Appendix A: Customizing Organization Settings NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
116
B
Tips and Tricks
The tips in this section are provided to help you find quick solutions to common situations and tasks.
Contents
To Display Details of Last Login ................................................................................. 118 To Change the User Name Format .............................................................................. 118 To Create a List of Invalid Passwords ........................................................................ 118 To Limit Invalid Login Attempts (Account Lockout).................................................. 119 To Add a New User to an Existing Profile .................................................................. 119 To Deactivate or Reactivate a System User Login ID................................................ 119 To Add System User Status to an Agent .................................................................... 119 To Record a System Users Interactions .................................................................... 119 To Define the Agent Identification for Screen Recording .........................................120 To Create a Limited All Users Group ..........................................................................121 Troubleshooting ...........................................................................................................122 Deleted Users are/are not Appearing in User Lists in Other Applications................122 Active Directory System Users cannot Log in to NICE Perform...............................122 Email for System-Generated Password is not Received by User ............................122 Profile Changes are not Activated............................................................................123 Some or all of the Agents (Traders) are Missing......................................................123 Some Agent (Trader) Information is Missing............................................................123 Some Functionality is not Working ...........................................................................123
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
117
In an Active Directory authentication environment, this option only applies if single sign-on is not implemented. (i.e., The user is not automatically logged in to NICE Perform after logging in to Windows. The user has to re-enter their login name and password in the NICE Perform login window.)
To display last login information: 1.
Select Organization and then click the Security tab. Expand the Security Options section.
Expand
2. 3.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
118
In the System User tab of the user definition, select User is a System User. Enter a Login Name and Password (twice). In the General tab, select User is a System User. Enter the identical Windows User Name and select the Domain for those defined in the Active Directory.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
119
Your primary site is in New York City. Your NICE Perform Web Server, Interactions Center, and NiceScreen Logger are installed at this site. In addition, your site includes three secondary sites - Boston, Philadelphia, and Elizabeth. At each of these sites, you have 200 agents (traders) whose screens need to be recorded. To ensure unique agent identification in this environment, you need to define the Agent Identification for Screen Recording value for each user. This value represents the branch where this user is located.
1. 2. 3.
Open the agents details for editing. See Displaying User Details on page 80. Click the Agent tab. In the Agent Identification for Screen Recording field, enter the agent location. For example, Boston or 1234.
TIP:
4.
This value must match the Identification String value defined in NICE ScreenAgent. For more information, see NICE ScreenAgent Installation Guide. This value must be typed without spaces.
Click Save.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
120
In the XYZ Investment Bank, when Matthew of the IT group logs into the Users Administrator, he sees only himself and Natalie in the All Users group. When Anthony logs in, all the users in the XYZ Investment Bank appear in the All Users group.
IMPORTANT If you have access to a group, but not directly to its users, they will appear in your All Users group for as long as they are part of the group. If you delete them from one of your groups, they disappear from your All Users group. Having access to a group does not give you access to its users when they leave the group.
Create a group with all the users you want in your All Users list. Create a New Profile. (See Profiles on page 49.) Add the group you created to the profile and select View and Edit privileges. In the Applications section, add access to the Users Administrator. Save the profile. Open a users details. Attach the profile. Close the Users Administrator and log in as the new user with the profile.
NOTE: The View Group Details privilege for the All Users group is selected by default and cannot be cleared. This means that a soon a system user acquires any profile, they will automatically be able to view their own All Users list.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
121
Troubleshooting
Troubleshooting
This section provides solutions to commonly asked questions. Deleted Users are/are not Appearing in User Lists in Other Applications Active Directory System Users cannot Log in to NICE Perform Email for System-Generated Password is not Received by User Profile Changes are not Activated Some or all of the Agents (Traders) are Missing Some Agent (Trader) Information is Missing Some Functionality is not Working
configured in the system, an email with a new password will not reach the user.
Solution: Since the request for a new password automatically changes the password, a manager
must enter the system and manually redefine a password for the system user as described in Manually Resetting Someone elses Login Password and Name on page 82.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 122
Troubleshooting
currently logged in to NICE Perform applications. The user does not seem to have the added privileges.
Solution: Have the user log out of NICE Perform and log in again as the same user. The new profile changes will be reflected.
In the open application, verify that the proper fields are displayed. Example: In the PBO Requests, click the Preferences button and in the Table View area, verify that the proper columns are displayed. Verify that the user has privileges to the correct Interactions data fields in the Users Administrator. See Attaching Profiles to Users, Group Members, or Group Managers on page 66.
2.
Appendix B: Tips and Tricks NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
123
C
Profile Privileges
Profiles can be created to meet specific needs. This section provides a complete list of available privileges and how they operate. Suggestions are given for creating basic, common profiles. Privileges included in predefined profiles are selected.
WARNING Predefined profiles can be modified by the system user at the site. Therefore, the actual privileges that appear for your predefined profiles may vary from their original settings.
Contents
Guidelines and Tips for Creating Profiles ..................................................................127 User Privileges..............................................................................................................128 Group Privileges ...........................................................................................................130 Applications Privileges ................................................................................................132 System Administrator Privileges ..............................................................................133 Users Administrator Privileges .................................................................................133 Business Analyzer Privileges ...................................................................................134 Form Designer Privileges.........................................................................................138 Monitor Privileges.....................................................................................................138 ROD (Recording On Demand) Privileges ................................................................138 Reporter Privileges...................................................................................................139 Lists Editor Privileges ...............................................................................................140 Rules Manager Privileges ........................................................................................140 Lexicon Manager Privileges .....................................................................................141 My Universe Privileges.............................................................................................141 ScreenSense Privileges ...........................................................................................142 Backup Manager Privileges .....................................................................................143 Insight Manager Privileges.......................................................................................143
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2) 125
Player Privileges ......................................................................................................145 Business Services Framework.................................................................................146 ClearSight Privileges................................................................................................146 Channel Monitoring ..................................................................................................147 Interaction Data Privileges...........................................................................................148 Selecting and Filtering Interaction Data Privileges...................................................149 Reporter Categories Privileges ...................................................................................151 Form Groups Privileges ...............................................................................................151 Query Folders Privileges .............................................................................................152
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
126
The applications they will be using and the tasks within each application that they need. The users (agents and/or system users) they are monitoring and managing. Do this through a group. The Data fields they need to view.
NOTE: NICE Perform has predefined profiles. You can use these as is, edit them, and/or create new profiles as needed. Among the predefined profiles is a profile to view all data fields. Add query and edit privileges in a separate profile as needed. For complete details, see Defaults Provided with NICE Perform on page 43.
Guidelines
Work with groups, not directly with users. Create a group for each job position and add users to groups. Even if a group has only one member. This allows you to work according to job positions and makes your system more modular. Attach profiles to groups and not directly to users. When adding users to a profile as a resource, add them as a group instead of directly.
NOTE: Profiles are updated internally in the system once every minute. A user logging in to the system before the update, will not receive the updated privileges. This scenario might occur if you add privileges to a user and then immediately log out and log in as the user with new privileges. Privileges relating to Form Groups and that allow users to view other users are updated once every hour.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
127
User Privileges
User Privileges
To give a system user the privilege to access (view, edit, query, record, playback) other users (agents and other system users), the user must be added to a profile as a resource and then the profile is attached to the system user.
EXAMPLE:
You want to give Supervisor Sal permission to locate and playback interactions made by Agent Adam. Open an existing or new profile and select Add Resource > Add User. Select Agent Adam and select the View/Query User, and Playback privileges. Attach this profile to Supervisor Sal. Generally, groups are created for each job position and then users are added to the groups as members. Profiles are attached to group members and privileges are given over groups not individual users. Accordingly, when users change job positions, they automatically receive the necessary profiles, and the managers of the groups they join, automatically receive permission over them. Use user privileges to achieve the following:
To assign users permission over themselves, allowing them access their own calls. Assign privileges to the Self user and include it with other necessary privileges. To allow a higher level user (manager) to track a specific user (such as a new employee) even when the employee changes positions.
IMPORTANT In addition to privileges to other users, the user must have privileges for the applications and the interaction data fields.
Agent
Business User
Administrator/ IT
X X
X X
X X
X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
128
User Privileges
Agent
Business User
Administrator/ IT
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
129
Group Privileges
Group Privileges
To give a system user the privilege to access (view, edit, query, record, playback) groups of agents and/or other system users, the groups must be added to a profile as a resource and then the profile is attached to the system user.
EXAMPLE:
You want to give Supervisor Sal permission to locate and playback interactions made by the Returns group. Open an existing or new profile and select Add Resource > Add Group. Select the Returns group and select the View/Query Group, and Play Members Interactions privileges. Attach this profile to Supervisor Sal. Generally, groups are created for each job position and then users are added to the groups as members. Profiles are attached to group members and privileges are given over groups not individual users. Accordingly when users change job positions, they automatically receive the necessary profiles, and the managers of the groups they join, automatically receive permission over them. Two groups appear in every profile. You can add additional profiles as needed.
Any Managed Group
Use this group to assign privileges that you want managers to have over all their group members. Users who receive a profile containing privileges selected for this group automatically receive these privileges over all members of all the groups for which they are a manager. A user with privileges for Any Managed Group who is not a manager of any groups, does not gain any privileges from this profile.
EXAMPLE:
Agent Wilma is a member in two groups: the Complaints group and the New Accounts group. She is a manager in the New Accounts group. Agent Wilma has a profile with the Record Members privilege for Any Managed Group. She can initiate recording for all members of the New Accounts group, but not of the Complaints group.
All Users
When you attach a profile containing privileges for this group, the receiver of the profile then has these privileges over all the users in the organization, or in their All Users group.
Create groups according to job positions and work groups. Then attach privileges to these groups. Use group privileges to achieve the following:
Give managers privileges over all the users that they manage. Assign them in Any Managed Group. Then attach the profile to group managers. Give managers privileges over specific groups. Add the group as a resource to a profile and attach it to the Managers Profiles tab for the group.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
130
Group Privileges
Agent
Business User
Administrator/ IT
A M G A M G
A M G A M G
A M G A M G
A M G A M G A M G
Use the record all interactions feature to record each group member from within applications where it is available (ROD, Monitor, etc.).
Record members
Use the record current or record next interaction features to record each group member from within applications where it is available (ROD, Monitor, etc.). Requires separate privileges to use the other applications. Evaluate all the interactions of all the groups members. Requires Query privileges for Business Analyzer.
A M G A M G A M G A M G
A M G A M G A M G A M G A M G
A M G A M G A M G A M G
Evaluate members
Calibrate members
Calibrate the evaluations of all the groups members. Requires Query privileges for Business Analyzer.
Use Business Analyzer privileges for Query Evaluations, Query Coaching Packages, and for creating My Universe Views for this groups members.
AMG indicates that this privilege is assigned to the Any Managed Group group. AU indicates that this privilege is assigned to the All Users group.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
131
Applications Privileges
Applications Privileges
The privileges for each application are listed in the following sections. In addition to application privileges, users will need permission to the relevant Interaction Database fields and to Users (this can be done via the groups to which the users belong).
TIP: Your system comes with some predefined profiles. One of them, Basic Columns, has permission to the most used data fields and is attached to the All Users group.
System Administrator Privileges on page 133 Users Administrator Privileges on page 133 Business Analyzer Privileges on page 134 Form Designer Privileges on page 138 Monitor Privileges on page 138 ROD (Recording On Demand) Privileges on page 138 Reporter Privileges on page 139 Lists Editor Privileges on page 140 Rules Manager Privileges on page 140 Lexicon Manager Privileges on page 141 My Universe Privileges on page 141 ScreenSense Privileges on page 142 Backup Manager Privileges on page 143 Insight Manager Privileges on page 143 Player Privileges on page 145 Business Services Framework on page 146 ClearSight Privileges on page 146 Channel Monitoring on page 147
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
132
Applications Privileges
Agent
Business User
Administrator/ IT
Use application
Add users to your employee database Designate users as agents whose interactions can be monitored and recorded Designate users as system users with privileges to access this and other NICE Perform applications Designate users as managers with privileges to supervise other users Create groups of users for managerial purposes Set up global password and security options for all system users logging into any application (In an Active Directory environment, password and security options are determined by the operating system)
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
133
Applications Privileges
Agent
Business User
Administrator/ IT
X X X X
Running queries (searches) to locate recorded interactions. Sites that have Audio Analysis, Feedback, or ScreenSense can run special queries according to each feature. Playing back interactions via the Media Player. Evaluating the performance of the agent who handled the interaction. Running queries to locate specific evaluations, calibrate the evaluations to ensure accuracy and then analyze agent performance. If your site includes Feedback, you can run queries to locate specific feedback surveys, review the surveys, and listen to customer comments. Using the Audit Trail module to locate and analyze system messages. Querying and creating Clips and Coaching packages to send to agents.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
134
Applications Privileges
NOTE: All Business Analyzer modules contain public and private folders. Queries/containers saved in a private folder can only be accessed by the owner of the folder (the user who saved the query/container) without additional modify or delete privileges. Queries/containers saved in a public folder can be modified or deleted by other Business Analyzer users who are assigned the appropriate privileges.
Users must be given the privilege to use each module separately. The basic privilege for each module is Query. The query privilege for each module allows the user to do the following:
Open the module and run predefined public queries. Create, run, modify, and delete their own private queries and folders.
System User Jane has the Query Interactions and Query Evaluations privileges. She can open these two modules and run predefined public queries. The single privilege, Add/modify/delete public query, is added to one of Janes profiles. Jane can now add, modify, and delete public queries in both the Interactions and Evaluations modules.
Agent
Business User
Administrator/ IT
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
135
Applications Privileges
Business Analyzer Privileges (Continued) Privilege Gives the user permission to...
Create/modify/delete Saved Items containers in the public folder in any module for which the user has Query privileges. Saved items containers created by a user are owned by that user. Requires any Query privileges for this application. Modify/delete public Saved Items containers owned by others in any module for which the user has Query privileges. Requires any Query privileges for this application. Create comments to interactions or evaluations. Comments created by a user owned by that user. Modify and delete comments owned by the user. Requires Query Interactions or Query Evaluations privilege. Modify/delete comments owned by others. Requires Query Interactions or Query Evaluations privilege.
Agent
Business User
Administrator/ IT
Create/modify/delete public Saved Items containers owned by the user Modify/delete Saved Items containers owned by others Create/modify/delete comments owned by the user Modify/delete comments owned by others
Interaction
Query Interactions Run predefined public queries in the Interactions module. Requires View/Query privileges for agents. Use the Analyze on Demand tool to select interactions for audio analysis. Requires Query Interactions privilege. Instant word search View Transcription Run Instant Word Searches View the Transcription preview pane by enabling the View Transcription option. Allows the user to extend retention of a specific call or calls. Requires the call to be in the Business Analyzer results grid. Allows the user to see the Exceptions preview pane when highlighting an interaction/contact. Also allows the user to filter interactions/contacts that have exceptions during interaction/recordings.
X X
Analyze on demand
X X X X
Extend Retention
View Exceptions
Evaluation
Query Evaluations Modify/delete evaluations owned by others Modify/delete calibrations owned by others Evaluate Customer Experience Run predefined public queries in the Evaluations module. Requires Query and Query Evaluations privileges for agents. Modify/delete evaluations owned by others. Requires Query Evaluations privilege. Modify/delete calibrations owned by others. Requires Query Evaluations privilege. Run a Customer Experience Evaluation. Requires Query Evaluations privilege.
X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
136
Applications Privileges
Business Analyzer Privileges (Continued) Privilege Gives the user permission to...
Modify/delete a Customer Experience Evaluation. Requires Query Evaluations privilege.
Agent
Business User
Administrator/ IT
Packages
Create/modify/delete public Packages owned by the user Delete Packages owned by others Query Packages Create public packages. Packages that are created by a user are owned by that user. Modify and delete public packages owned by the user. Requires Query Packages. Modify and delete public coaching package owned by others. Requires Query Packages. Run predefined public queries in the Coaching module. Requires Query and Query Evaluations privileges for agents.
X X X X X
Feedback
Query Feedback View Feedback details Run predefined public queries in the Feedback module. Requires View/Query privileges for agents. Open the Feedback Viewer to see individual survey results.
X X
X X
X X
Audit
Query Audit Trail Run predefined public queries in the Audit Trail module. Requires View/Query privileges for agents.
eLearning
Assign courses Assign eLearning courses to users for whom you have View/Query privileges.
Clip
Query Clip Recordings Run predefined public queries in the Clips module. Requires Query and Query Evaluations privileges for agents. Create public clip recordings. Clip recordings that are created by a user are owned by that user. Delete public clip recordings owned by the user. Requires Query Clip Recordings privilege. Delete public clip recordings owned by others. Requires Query Clip Recordings privilege.
X X
X X
X X
Create/delete public Clip Recordings owned by the user Delete Clip Recordings owned by others
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
137
Applications Privileges
Agent
Business User
Administrator/ IT
X X
Monitor Privileges
Users with privileges for the Monitor application can listen to calls and view screen activity in real time, and initiate recording.
Monitor Privileges Privilege Gives the user permission to...
Open and use the Monitor application.
Agent
Business User
Administrator/ IT
Use application
Agent
Business User
Administrator/ IT
Use application
X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
138
Applications Privileges
Reporter Privileges
Reporter privileges are needed by users who will be creating customized reports and reporting schedules. Users who are viewing reports off-line (via email, saved file, hard-copy, etc.) do not need access to the Reporter application. Users who are viewing reports on-line (via My Universe) need Login and Viewing privileges to Reporter application. They also need privileges to My Universe.
NOTE: You will need Report templates to create reports. These are available through Reporter Categories. Privileges for Reporter Categories must be given separately. See Reporter Categories Privileges on page 151.
Agent
Business User
Administrator/ IT
Use Application
X X
X X
X X
X X
X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
139
Applications Privileges
Lists used by the Form Designer to create forms for evaluations. Departments and Location lists found on the Details tab of the User definition in the Users Administrator. Coaching Categories.
Agent
Business User
Administrator/ IT
Use application
Agent
Business User
Administrator/ IT
X X X
X X X
Use Classification
X X
X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
140
Applications Privileges
Agent
Business User
Administrator/ IT
Use application
My Universe Privileges
My Universe is a visual representation of key data from NICE Perform. It is a customized portal to the NICE Perform applications, providing immediate access to the essential data that is pertinent to the user. My Universe is composed of different windows displaying components of up-to-date data: Each window enables the user to look at the data provided by NICE Perform from a different perspective. Some windows are relevant to high level business managers who want a quick glance at the overall level of performance in the site. Some windows are relevant to supervisors who want to see how well the agents that they supervise are performing. Other windows are relevant to agents who can see how well they are performing compared to their colleagues over a period of time. Using the View Manager, you can define which components are available for other users to view in My Universe. In addition to privileges to use the My Universe application, the user will need privileges to the applications viewed in My Universe.
Agent
Business User
Administrator/ IT
X X
X X
X X
X X X
View Manager
Use View Manager Application User can open the View Manager.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
141
Applications Privileges
Agent
Business User
Administrator/ IT
X X
ScreenSense Privileges
ScreenSense enables you to create voice and screen interactions, create recordings and extract information that appears on the agents screen to the database based entirely on what takes place on an agents screen. ScreenSense gives you the power to capture your agents voice, and/or screen, whenever an Event of your choice takes place. These recordings are tagged, enabling easy searches, retrieval and evaluation of the interactions. Using the ScreenSense Manager, you create Events. When an agent performs a specific activity at his/her workstation (Trigger), a value from the agents screen is extracted to the database (Screen Object) and/or a predefined flow (Action) takes place.
ScreenSense Privileges Privilege Gives the user permission to...
Start ScreenSense wizard and view ScreenSense events and groups of events. Edit ScreenSense events and groups of events. Requires View Events and Event Groups privilege. View attachments of group events. Modify attachments of group events. Requires View attached Events to Users or User Groups privilege.
Agent
Business User
Administrator/ IT
Use application Edit Events and Event groups View attached Events to users or user groups Edit Events attachment to users or user groups
X X X X
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
142
Applications Privileges
Agent
Business User
Administrator/ IT
Use application
What are the reasons for customer calls (product inquiries, billing issues, promotions, cancellations and so on). What are the top service issues (lost delivery, damaged products, missing items and so on). Identify cross-sell/up-sell attempts made by agents Identify interactions in which a competitor name was mentioned by the customer.
For each task, you can define words/phrases that the task will try to detect within a specified set of interactions, thereby providing a powerful analysis tool. The Insight Manager enables hindsight analysis (analysis of past interactions) and foresight analysis (analysis of ongoing interactions). This analysis is carried out by running different types of tasks.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
143
Applications Privileges
Agent
Business User
Administrator/ IT
X X
X X
X X
X X X X
Modify and delete Monitoring Procedures owned by others for whom the user has View/Query privileges. Run or stop Monitoring Procedures owned by others for whom the user has View/Query privileges. View the results in Business Analyzer.
General
Create/modify/delete public queries owned by the user Modify/delete public queries owned by others Create/modify/delete public Saved Items containers owned by the user Create a public query to find tasks. Queries created by a user are owned by that user. Modify or delete public queries owned by the user. Modify or delete public queries owned by others for whom the user has View/Query privileges. Create Saved Items containers in the public folder. Saved Items containers created by a user are owned by that user. Modify or delete public Saved Items containers owned by the user.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
144
Applications Privileges
Agent
Business User
Administrator/ IT
Player Privileges
The Player enables you to play back voice and/or screen interactions via your telephone or speakers. The Player can be accessed in two modes:
Applications Suite Mode: In this mode, the Player is opened when you select an interaction and click Play from within one of the NICE Perform applications. You can play back the
interaction and display the interaction sound waves. In this mode, the Player displays information about the interaction activity (when an agent/customer is speaking) and the interaction events (word-spotting events, ScreenSense events, annotations and excitement levels). You can add annotations to an interaction, display/hide interaction events, save an interaction to your desktop and send an interaction as an email attachment. In addition, you can define the Player output type and Player preferences.
Standalone Mode: In this mode, the Player must be opened manually from your desktop.
After the Player is opened, you can select an interaction (NMF file or AUD file) for playback and display the interaction sound waves. In addition, you can save an interaction under a different file name and send an interaction as an email attachment.
Agent
Business User
Administrator/ IT
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
145
Applications Privileges
Agent
Business User
Administrator/ IT
Business Services Framework Privileges Privilege Gives the user permission to...
Open and use Business Services Framework.
Agent
Business User
Administrator/ IT
Use framework
ClearSight Privileges
ClearSight performs analysis on a set of interactions that were previously grouped together in a category using Insight Manager.
Agent
Business User
Administrator/ IT
Use application
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
146
Applications Privileges
Channel Monitoring
Channel Monitoring enables administrators and technicians to monitor channels according to each specific logger at a site to make sure they are working properly. They can also play back recordings of channel activity that were recorded from each channel, as well as play the channel activity (monitor) in real time.
Agent
Business User
Administrator/ IT
Use application
X X
Play channel
Monitor channel
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
147
Your system comes with a predefined profile called Basic Columns. It includes View and/or Query privileges to the Interaction Data fields needed by most system users. Some of the Interaction Data fields included in the Basic Columns profile are required for internal use. Do not remove these! See the Interaction Data Reference Guide for an itemized description of the interaction data fields. Interaction Data privileges cannot be added to a default profile. When a data field is attached to a user/group, you must give privileges separately.
Agent
Business User
Administrator/ IT
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
148
View privileges for the data field for users/groups with the profile. Users/groups with the
You can filter the data available in selected data fields. This gives the user/group with the profile permission to view, edit and/or query this data field (depending on the privileges enabled) for the values defined by the filter only. The filterable option is predefined with your system and cannot be edited by the user.
EXAMPLE:
The data field is Last Name and you apply a filter for names less than b. Only those names that begin with a will be available to whoever receives this profile.
To select and filter Interaction data privileges: 1. 2.
In the Organization tree, click Profile, then in the General tab, select a profile. Click Interaction Data.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
149
3. 4. 5.
Locate the required data field in the Column name column. Select View, Edit, and/or Query as required. These privileges must be enabled globally in the System Administrator database definition to be able to assign them here. To filter a data field, the data field must be selected as Filterable. The Filterable option is predefined with your system installation. Double-click the Filter cell of the required data field. The Filter Settings window appears.
6. 7. 8.
to exit the Select Interactions data privileges window. to save the changes.
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
150
Use category
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
151
Appendix C: Profile Privileges NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
152
D
Sample Contact Center
Initial setup up of your company structure takes time and planning. Once you install your basic structure and understand the flow of command, maintaining your company structure will be a simple task. We provide a scenario of the fictitious company, the ABC Contact Center, as a sample to help you understand the flow of command. See Figure D-1 on page 155 for a diagram of the ABC Contact Center.
Contents
Overview of a Sample Contact Center........................................................................154 Sample Structure ..........................................................................................................156 Working the System - Examples .................................................................................157
Appendix D: Sample Contact Center NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
153
The IT division is a small division whose members are all on the same level. They supervise the daily running of the system and applications. They control Login options, user IDs and password information. IT employees are not monitored. They do not need to be defined as agents. They require access to all applications and other resources. They are defined as system users. The IT manager reports directly to the ABC Contact Center manager. The Phone Services division is a larger division made up of several departments. The members of each department are agents in charge of handling different types of telephone requests. It has two high-level managers and is divided into four departments (subgroups). Each department has a group manager and several employees. The entire Phone Services division, including the managers, is monitored. Therefore, they must all be defined as agents. Each manager will be using the system applications and must also be defined as a system user. The following diagram shows the ABC Contact Center organizational structure.
Appendix D: Sample Contact Center NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
154
Anthony (Manager)
Phone Services
IT
Matthew (Manager)
Natalie
Complaints
Orders
New Accounts
New Employees
Dennis (Manager)
Mary Charles Susan
Tina (Manager)
Jonathan Sammy Marjorie
Linda (Manager)
Susan Sammy
Appendix D: Sample Contact Center NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
155
Sample Structure
Sample Structure
IMPORTANT Profiles work in combination, not separately. Thus, if you receive the privilege to view agent Jane from one profile and the privilege to playback interactions from another profile, you can playback agent Janes interactions.
TIP: Attach all profiles using the Profiles or Managers Profiles tab for each group and not directly to users. In this way, if users change groups or managers of groups change, each user/manager receives the appropriate profile.
The following is a sample of how you might create and assign some profiles in the ABC Contact Center. Working the System - Examples on page 157 deals with some changes that might occur based on the scenario below.
1.
All ABC employees can use My Universe to view their evaluations. They must all be defined as System Users with access to use My Universe and Use application privileges to the Business Analyzer. These privileges will be included in one profile called Review Evaluations. Attach it to the All Users groups profiles tab. Each group manager (Dennis, Millicent, Jane, Tina, and Linda) must be given the privilege to monitor and playback their entire groups calls. They will be given all privileges for Any Managed Group except for Evaluate and Calibrate. They will also receive privileges to the Monitor and ROD applications. These privileges will be included in one profile called Manager Level1. Attach it to the managers profiles tab for the Complaints, Orders, New Accounts, and New Employees groups. High-level managers (Alfred and Betty) must be able to monitor and playback the calls made by all the groups below them (Complaints, Orders, New Accounts, and New Employees). They need the Manager Level1 profile. Attach it to the managers profiles tab for the Phone Services group. The high-level managers evaluate each agents performance. They require access to the Business Analyzer and the privilege to evaluate and calibrate the members of all their groups. Create a profile called Manager Level2 with Evaluate and Calibrate privileges for Any Managed Group and all privileges for the Business Analyzer except for modify/delete others. Attach it to the managers profiles tab for the Phone Services group. The ABC Administrator (Anthony) sets up recording schedules and therefore requires access to the Rules Manager. Call it Administrator. Attach it to the managers profiles tab for the ABC Contact Center group (this is the top level group and can be the Groups folder). The agents in the Complaints group also create and run reports. They require a profile with privilege to the Reporter, excluding the Reports Administrator. Call this profile Reporter. Attach it to the profiles tab of the Complaints group. The New Employees group consists of recently hired agents from other groups. They require special attention. Therefore, their direct manager evaluates their performance. Linda requires access to the Business Analyzer. Attach the Manager Level2 profile to the managers profiles tab of the New Employees group.
Appendix D: Sample Contact Center 156
2.
3.
4.
5.
6.
7.
You realize that the system users using Rules Manager also require privileges to the Lists Editor. Add the Lists Editor Privileges to the Administrator profile. Anthony automatically gains these privileges. (Item 5 in Sample Structure on page 156) Mary moves from the Complaints group to the New Accounts group. Mary automatically loses the Reporter profile and thus privileges to the Reporter. (Item 6 in Sample Structure on page 156) Jane leaves the Orders groups and becomes a manager of the New Employees group. She automatically gains the Manager Level2 profile (Item 7 in Sample Structure on page 156). She loses privileges over the employees of the Orders group, but gains privileges over the employees of the New Employees group. A new department, Holidays, is created to deal with special holiday promotions. Linda is asked to expand her services and evaluate this new department while not being a manager of that department. This is a special task that will be performed only by Linda. If she is replaced, her replacement will not be performing this task. Create a new profile called Eval Holidays. Add the Holidays group as a resource to this profile with full privileges. Attach this profile directly to Linda on her users profiles tab. (Linda already has privileges for evaluating from the Manager Level2 profile she received as manager of the New Employees group [Item 7 in Sample Structure on page 156], she now required access to the users of the Holidays group.)
2.
3.
4.
Appendix D: Sample Contact Center NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
157
Glossary
Active Directory Authentication NICE Perform interfaces with Windows Active Directory. Each system user is defined in the Active Directory by a unique Windows User Name and Domain. The user is then defined in NICE Perform with the exact same Windows User Name and Domain. NICE Perform interfaces directly with your operating system and uses the values in the Active Directory to authenticate each system user. In this environment, you do not define an additional login name and password in NICE Perform, since the users actual Windows User Name and password are used to log in to NICE Perform. Password policy is determined by Active Directory. See also NICE Perform Authentication
Agent A user whose calls are recorded. Agents can be a member of a group and/or the group manager. Agents do not need access to system resources or to other users or applications. Agents can be traders, brokers, or back-office personnel.
Group A set of users who are united for the purpose of assigning like privileges. A user can be a member in more than one group. A group must have at least one manager.
Interaction An Interaction is any call made by or to an agent and logged in the system. Interactions can be recorded and played back. Voice interactions can also be archived. Interactions can also be logged in the system as having occurred without saving the actual interaction.
Manager A user in a group who has special privileges over the other users. Privileges assigned to a groups manager are not automatically assigned to the groups users. A group can have more than one manager.
Glossary NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
159
NICE Perform Authentication Each system user is defined in the NICE Perform system by a unique login name. The user uses this login name, and the password defined with it, to log in to NICE Perform. See also Active Directory Authentication
Profile A profile is a set of privileges. Profiles are attached to users or to groups. Each user can have many profiles. If the privileges in a profile are changed, they automatically change for all the users who were previously given that profile.
Recorded Interaction A Recorded Interaction is an interaction that occurred in the past and is stored for future playback. Recorded Interactions can be locked to prevent automatic deletion, archived, and sent via email.
System User A user who uses the applications to supervise the system and other users. System users whose interactions are recorded must be defined as agents.
User Anyone defined in NICE Perform. Users can be agents and/or managers. Users can be assigned privileges to access other users and system resources (system users). Anyone using the system in any capacity (logging into applications, being recorded, etc.) must be defined as a user.
Glossary NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
160
Index
A
Users Administrator 60 data fields see also business data activating system user accounts 88, 89 Active Directory changing login and password 85 deactivating/activating system user accounts 89, 119 defining login name 74 displaying domains 116 overview 32 troubleshooting login 122 Administrator/IT, predefined profile 43 agent ID adding 91 as agent identification 33 agent identification 76 agents see also users adding system user status 119 overview 28, 71 troubleshooting 123 types of identification 33 All Users group, Users Administrator creating 121 described 30 folder 30 predefined user 45 Any Managed Group, Users Administrator described 52 applications privileges to 132 applications, Users Administrator adding permission to in a profile 57 authentication 32 auto logout settings 112 Basic Columns, predefined profile 44 Basic Recordings, predefined user 43 Business Analyzer privileges to 134 business data
ClearSight privileges to 146 Compliance, predefined profile 44 contact center sample 153 contents pane, Users Administrator 21 data fields 60 adding as a profile resource 63 deactivating system user accounts 88, 89 defaults, Users Administrator 43 deleted users troubleshooting 122 Users Administrator 23, 93 deleting users 92 details pane, Users Administrator 25 display names 21, 118 domain displaying in selection lists 116 extension, as agent identification 33
E F
folders pane, Users Administrator tips 15 forbidden passwords, setting 109 Form Designer privileges to 138 Form groups privileges to 151 formatting user names 21, 118 groups searching 16 groups of users adding a manager 102 adding as a profile resource 55 adding members 100
Index 161
attaching profiles 66, 104 before you begin 96 creating 97 creating All Users 121 deleting 104 described 37 hierarchy 37 imported 47 overview 28, 95 privileges to 130 removing members 100 sample structure 153 showing details 38
defining a group manager 102 removing from a group 100 minimum password age, setting 108 Monitor privileges to 138 My Universe privileges to 141
N O P
H I
identification agent, Users Administrator 76 imported users and groups 47 inherited profiles, rules of 40 Insight Manager privileges to 143 interaction data filtering in profiles 149 privileges to 148
Lexicon Manager privileges to 141 Lists Editor privileges to 140 Logger Backup privileges to 143 login details 111 Login window displaying last login 118 login, system users changing 85 deactivating and reactivating 88, 89 default 44 setting password restrictions 106 setting security 110, 112 managers of groups adding to a group 102 attaching profiles 66 maximum password age, setting 108 members of groups adding to a group 100
password settings checking requirements 109 expiration for individual system users 86 expiration period 108 forbidden 118 history 109 options described 107 restricting for individual system users 106 password troubleshooting 122 Player privileges to 145 privileges see also profiles adding to a profile 62 Administrator/IT predefined 43 Basic Columns predefined 44 described 125 for applications 132 for groups 130 for users 128 overview 28 sample structure 153 Security Administrator predefined 43 profiles see also privileges adding a user 119 adding applications to 57 adding data fields to 63 adding Query Folders to 58 adding Reporter Categories to 57 adding users and groups to 55 attaching 66 attaching directly to users 89 attaching to groups 104 before you begin 52 creating 54
Index 162
deleting 69 described 40 editing privileges 62 guidelines and tips 50, 127 inheritance rules 40 overview 28, 49 privileges described 125 sample structure 153 showing details 42 system defaults 43 troubleshooting 123
account lockout 119 activating and deactivating 88 authenticating 32 customizing details 80 deactivating/reactivating login accounts 119 defining identification 77 forbidden passwords 118 overview 28, 71 recording 119
Query Folders adding permission to in a profile 58 Query folders privileges to 152 reactivating system user accounts 88, 89 Reporter privileges to 139, 151 Reporter Categories 64 adding applications to 64 adding permission to in a profile 57 ROD (Recording On Demand) privileges to 138 Rules Manager privileges to 140
Trader, predefined profile 44 traders see also agents overview 28 troubleshooting limited functionality 123 missing agent information 123 missing agents 123 profile changes 123 Unmapped User, predefined user 43 user names, formatting 21, 118 user password, setting 108 users see also agents see also system users see also Active Directory adding agent ID 91 adding as a profile resource 55 adding to a profile 119 attaching profiles 66, 89 authenticating 32 before you begin 72 creating 73 customizing system user details 80 defaults 43 deleting 92 described 31 editing details 80 imported 47 overview 71 predefined 43 privileges to 128 sample structure 153 searching 16 showing details 34 using the Self user 45 Users Administrator deleted users 23, 93 formatting user names 21, 118
Index 163
sample, Users Administrator contact center 153 organization structure 156 screen recording agent identification 76 ScreenSense privileges to 142 searching for users and groups 16 Security Administrator, predefined profile 43 security settings activating individual system users 88 Active Directory 89 options described 112 organization level 110 Self user, Users Administrator 45, 52 Superuser, predefined profile 43 Superuser, predefined user 43 System Administrator privileges to 133 system users see also Active Directory see also users
hierarchy overview 28 navigating 14 organization settings 105 organization structure 156 overview 11
Index NICE Perform Release 3.1: Users Administrator Guide (Rev. A2)
164