Users Overview

Users are individuals who have access to and can perform tasks in the NICE Uptivity Web Portal. They also appear in NICE Uptivity Web Portal searches and in NICE Uptivity reporting. Users may include agents, supervisors, system administrators, and others.

AgentsClosedThe person or people taking the inbound calls. are users who have the Agent field selected in their user accounts. Their audio interactions (and screens, if applicable) are typically recorded. For more information, see Configuring Users for Recording.

Users must have a user account in order to log in to the NICE Uptivity Web Portal. By default, users can log into the NICE Uptivity Web Portal and view the Home tab and the Coaching tab's Content Library. In the library, they can only see documents that have been assigned to them. Other tasks that users can perform are defined by their assigned role(s), and you should typically create roles before creating user accounts. For more information, see Roles and Permissions Overview.

Login Modes

The type of authentication, or login mode, used in your system is decided and configured during installation. Uptivity supports three login modes:

  • Database Mode — Validates logins against users in the Uptivity database. With this mode, you must create accounts for users in the database before they can log in. Password length and other security measures are configured in Uptivity. This is the default login mode.
  • Active Directory (AD) Mode — Validates logins against AD using Kerberos authentication. The user must be logged into AD and be a member of an AD group with permissions to access Uptivity. With this mode, user accounts may be created automatically the first time the user logs in to the NICE Uptivity Web Portal using AD credentials. Password length and other security measures are configured in AD. Additional settings must be configured to support this login mode.

    When users log in using AD authentication, a message is sent from Uptivity to AD. This event is logged, as is the result, which can be:

    • Uptivity receives a response from AD and authentication succeeds. The user is logged in.
    • Uptivity receives a response from AD and authentication fails. The user is not logged in, and a specific message identifying the cause is logged.
    • Uptivity fails to receive a response from AD. In this case, a "Directory Entry Failed" error is logged and the user is not logged in. There is no timeout associated with this; it either succeeds or fails. On the Uptivity login screen, the following message is displayed: "Login failed. No response was received from Active Directory or Active Directory could not be contacted."

Uptivity version 18.x no longer supports SSO with SAML v2.0. To use this feature, you must have Uptivity version 20.1 or later.

Managing User Accounts

In many contact centers, users change frequently. Uptivity provides three ways to handle user accounts when a user's status changes. For more information on these, see Users.

  • Locking
  • Deactivating
  • Deleting

At times, you may want to create or update user accounts in batches (for example, if a new center comes online, a new department begins recording, or new phone numbers are issued to a group of recorded agents). If you have a database or Excel spreadsheet of agents, you may be able to generate a comma-separated values (CSV) data file that you can then import into Uptivity, saving time by minimizing data entry tasks.

You can also export user account information from the Uptivity database to a CSV file. You may use this file as a backup or to import the data into other applications. The file will contain the same values for each user as those required for an import file. Therefore, if a batch of agents needs updating, you could export the file, make the changes, and then import the same file.

User account data can be added to or extracted from the Uptivity database via the Uptivity API. For more information, see API Overview or talk to your Uptivity representative.