Chapter 04. Role Administration

About Role Administration

A role is a classification applied to users and teams to control access to functions of the Administration Server, and to define the criteria for assigning work. The role defines the "personality" of the user or team that uses it to log into the Administration Server.

 

Access and Configuration

The Role Administration function allows you to define whether a user who is assigned a particular role can:

  • Access one or more queues
  • Have role-specific skills and work item utilization settings
  • Have alerts and notifications for new work assignments (not supported in this release)

 

Administrative Roles

The Role Administration function also allows you to define roles with administrative privileges. Roles define whether a user has permissions to:

  • Access Areas in Management Console
  • Be a Super User (with access to all areas of the Management Console)
  • Edit organization information

 

Logging into the Administration Server

When users log into the Administration Server, they specify a role that determines their "personality”. If the user has more than one assigned role, the Administration Server displays a page for the user to select one role.

If you create teams for your organization and assign a role to a team, then any user who logs into the Administration Server with that role is automatically a member of the team.

 

Skills

You can assign skills to roles to define the important abilities and aptitudes that apply to the role for working with applications. Skills are used to route work assignments using skills-based routing.

If skills differ between role, team, and individual user, users inherit skills based on the following order of precedence:

  • Skills assigned directly to the user override all other settings.
  • If skills are not assigned directly to a user, skills assigned to the team override all other settings.
  • If skills are not assigned to a user or a team, skills based on the skill - role Modifier override the other setting.
  • If all of the above skill settings are null, the system uses skills based on role assignment.

 

Utilization

You can assign utilization settings to roles. Utilization defines the workload capacity required for a user with this role to complete a work item of a given type. A work item that involves a customer phone call likely requires 100% of a user's capacity, while an emailed troubleshooting ticket may only require 50% utilization for a senior-level technician role.

If utilization settings differ between role, team, individual users, and the organization, users inherit utilization settings based on the following order of precedence:

  • Utilization settings assigned directly to the user override all other settings.
  • If utilization settings are not assigned directly to a user, team utilization settings override all other settings.
  • If utilization settings are not assigned to a user or a team, utilization settings based on the utilization - role Modifier override all other settings.
  • If utilization settings are not assigned to a user, team, or utilization - role Modifier, role utilization settings override the other setting.
  • If all of the above utilization settings are null, the system uses utilization settings associated with the organization.

 

Procedure: Administering Roles

To access role administration functions, click the Role Administration link on the Administration Home page. Clicking the Role Administration link launches the Role Administration wizard.

The Role Administration wizard allows you to:

  • Modify existing roles
  • Create new roles
  • Assign a queue to a role
  • Create a new queue
  • Assign role skills
  • Create new skills
  • Assign utilization settings to a role

The following diagram is a map of the role administration process (Part 1 of 2):

The diagram of the role administration process continues below (Part 2 of 2):

 

4.3 Role Administration Page

This section provides definitions for fields on the Role Administration page.

 

Fields

Role Name

The name of the role. Click the Role Name link to edit the role.

 

Operations

Create Role

This page includes a button to create a new role.

 

Edit Role Page

This section provides definitions for fields on the Edit Role page.

 

Fields

Role Name

The name of the role.

Role Description

A brief description of the role.

Alert Play Sound

Indicates whether users assigned the role will be given a warning sound when an alert occurs.

Alert Send Email Notification

Indicates whether users assigned the role will receive alert email messages when an alert occurs.

Is Super User

Indicates whether users assigned the role have full administrative capability within the organization, regardless of other role permission settings.

Distribute My Queue Work Items Only

Indicates that users assigned the role will only receive work items assigned to them, or to a team of which they are
a member.

Can Access Deployment Area

Indicates whether users assigned the role can access the Deployment area of the Management Console to deploy applications.

Can Access Deployment Target Area

Indicates whether users assigned the role can access the Deployment Target area of the Management Console to deploy applications.

Can Access JDBC Area

Indicates whether users assigned the role can administer JDBC data source settings.

Can Access Application Server Area

Indicates whether users assigned the role can access the Application Server area of the Management Console to view and manage active applications.

Can Start Up/Shut Down Application Server

Indicates whether users assigned the role can start up or shut down the Application Server in the Application Server area of the Management Console. This option is only available to users of the Master Organization.

Can Edit Organization

Indicates whether users assigned the role can modify the organization to which they belong.

Can Access Queue Area

Indicates whether users assigned the role can administer queues.

Can Access Role Area

Indicates whether users assigned the role can administer roles.

Can Access Skill Area

Indicates whether users assigned the role can administer skills.

Can Access Status Area

Indicates whether users assigned the role can administer status values.

Can Access Campaign Management

Indicates whether users assigned the role can administer campaigns.

Can Access Team Area

Indicates whether users assigned the role can administer teams.

Can Access Update StarPound Application and Agent Server

Indicates whether users assigned the role can access the Update Work Item Server area.

Can Access User Area

Indicates whether users assigned the role can administer users.

Can Access Utilization Area

Indicates whether users assigned the role can administer utilization settings.

Can Access Telephony Area

Indicates whether users assigned the role can administer telephony settings.

Can Access Switch Config Area

Indicates whether users assigned the role can administer switch configuration settings.

Can Access Custom Lib Area

Indicates whether users assigned the role can access the Library Administration Area.

Can Access Dashboard

Indicates whether users assigned the role can access the Dashboard.

Can Access Resource Pool Area

Indicates whether users assigned the role can access the Resource Pool Area.

After you have specified all the necessary settings for the role, click <Next> button, so that you will be able to setup a queue for the role.

 

Queue Setup for <Role> Page

This section provides definitions for fields on the Queue Setup for <Role> page.

 

Fields

Queue

Specifies which queues to associate with the role. Select a queue and click Add to Role to assign the permissions for the queue.

Queue Name

Indicates the queues that are currently associated with the role. Clear the checkbox next to the Queue Name field and click <Next> or <Finish> to remove the queue from this role. Click the Queue Name link to edit the permissions for the queue.

 

Operations

Create Queue

This page also includes a link to create a new queue.

 

Create Queue for <Role> Page

This section provides definitions for fields on the Create Queue for <Role> page.

 

Fields

Queue Name

The name of the queue.

Queue Description

A brief description of the queue.

Queue Type

Indicates how the queue handles new work items. Values are:
  • Pull, where users must retrieve items from the queue
  • Push, where work items with media (phone calls or live chat) are directed to users immediately when the item is assigned

Agent Alert Time (sec)

The length of time that the system waits for a work item in this queue to be accepted before the work item experiences
an alert timeout.

Alert Timeout Agent Status

(Not supported in this release) The user status value that the system sets, when the user fails to accept an assigned item within the specified agent alert time.

Statistics Period

(Not supported in this release) The length of the queue's statistics period. At the end of the period, counters
are reset to zero.

Time in Queue (sec)

The length of time the system waits for a work item in this queue to be accepted before the work item experiences a queue timeout.

Route Timeout (sec)

The length of time the system waits for a work item in this queue to be routed before the work item experiences a route timeout.

Media Queue

Select the media queue to associate with this queue.

After Work Time (seconds)

Set the length of time to wait after a user completes a task before the agent is available for another hot work
item assignment (one with an associated phone call).

Default Distribution Policy

Indicates the default distribution policy for the queue. This value is applied to any work item in this queue that is
assigned to a team without a distribution policy set at the team level. Values are:
  • Group Ring, where all available users are notified of the new work item.
  • Round Robin, where work items are distributed to available users in rotation. The first item is assigned to the first user, the second to the second user and so on.
  • Sequential, where work items are distributed in priority order, always starting with the first user in the defined sequence. If the first user is not available, the item is distributed to the second user or the next available user in the sequence.

 

Permissions for <Role> on <Queue> Page

This section provides definitions for fields on the Permissions for <Role> on <Queue> page.

For each role, you must grant permissions for the users with that role to accomplish activities on each queue for each work item type. If you do not grant permission on the queue for a work item type, users with that role will not see work items of that type, even if their role includes access to the queue. You cannot grant access to a queue without granting permissions.

For example, you might grant permission for users with the Tech Support role to accept PC troubleshooting work items on the Help Desk queue. Without that permission, users with the Tech Support role would not see items with that work item type in the queue.

In order to grant permission to a work item type for this role and queue, you must first create a work item type in the Utilization area.

 

Fields

Work Item Type

The work item types associated with the organization. Check the checkbox next to the Work Item Type fields to give
this role the indicated permission for the work item type on the queue.

Permission

The permission you can grant to the role for the work item type. Permission types include:
  • Accept. Permits users to accept work items with the specified work item type on the queue.
  • Listen In. Permits users to listen into phone calls associated to work items.
  • Transfer. Permits users to transfer an assigned work item to another user.
  • End. Permits users to end an assigned work item using the End button on the Media Control bar.

 

Skill Factors for <Role> Page

This section provides definitions for fields on the Skill Factors for <Role> page.

 

Fields

Skill Name

The name of the skill.

Skill Value

The name of the skill value associated with the skill.

Proficiency

A percentage that defines how proficient the user is with the skill when compared to other users.

Desire to Use

A percentage that defines how often the user should use the skill in relation to other users and in relation to the user's other skills. You might use this percentage to indicate that, in spite of a high proficiency, a senior-level user should use this skill only as a backup for junior-level users.

 

Operations

New Skill

This page includes a button to create a new skill.

 

New Skill Factor Page

This section provides definitions for fields on the New Skill Factor page.

You can enter up to three skill and skill value combinations on this page.

 

Fields


Skill Name

Select an existing skill to create a new skill value or to assign Proficiency or Desire to Use settings.

New Skill Name

Enter a name to create a new skill.

Skill Value

Select an existing skill value associated with the skill to assign Proficiency or Desire to Use settings.

New Skill Value

Enter a name for a new skill value to associate with the specified skill name.

Proficiency

A percentage that defines how proficient the user is with the skill when compared to other users.

Desire to Use

A percentage that defines how often the user should use the skill in relation to other users, and in relation to the user's other skills. You might use this percentage to indicate that, in spite of a high proficiency, a senior-level user should use this skill only as a backup for junior-level users.

The next step is setting up Utilization for <Role> page.

 

Utilization for <Role> Page

This section provides definitions for fields on the Utilization for <Role> page.

In order to add utilization settings for this role, you must first create a work item type in the Utilization area.

 

Fields

Work Item Type

Select a work item type that has not yet been assigned to this role, and click the Add Utilization button to create new
utilization settings.

Work Item Type Name

The name of the work item type for this utilization. Check the checkbox next to the Work Item Type Name field and click
Save to remove the work item type utilization from this role.

Percent Utilization

A relative value, expressed as a percentage, that indicates how many work items of this type that the system will route to a user with the role. This percentage is subtracted from a user's capacity when a work item of this type is assigned. For example, if the Percent Utilization for work item type "X" is set at 25%, a user could receive up to four "X" work items before
the system recognized the user as fully utilized. If the Percent Utilization for work item type "Y" is set at 10%, the user
could receive up to ten "Y" work items before the system recognized the user as fully utilized. This percentage applies to all work items routed to the user, not just the total percentage of a single work item type. For example, if the user received 2 "X" work items and 5 "Y" work items, the system would recognize the user as fully utilized.

Max Assigned

A number, expressed as an integer, which indicates the maximum number of work items of this type that the system will
route to a user with this role. For example, if the Max Assigned setting for work item type "A" is "3," all users with this
role can receive no more than three "A" work items. However, unlike Percent Utilization, the Max Assigned values for a given
work item type do not accrue against other work item types. For example, if the Max Assigned setting for work item "A" is "3" and the Max Assigned for work item "B" is "4," the system does not recognize the user as fully utilized when the user
receives three "A" work items, since the user may also receive up to four "B" work items.

Inherited Percent Utilization

The Percent Utilization for work items of this type, as defined at the organization level.

Inherited Max Assigned

The maximum number of work items of this type that can be assigned to a user, as defined at the organization level.

Inherited Source

The source from which this work item type inherits utilization settings. For a role, utilization is always inherited from the organization default settings for the work item type.

 

Operations


Add Utilization

This page includes a button to create a new work item utilization.

 

Edit Utilization for <Role> Page

This section provides definitions for fields on the Edit Utilization for <Role> page.

 

Fields

Work Item Type Name

The name of the work item type.

Percent Utilization

A relative value, expressed as a percentage, that indicates how many work items of this type that the system will route to a user with the role. This percentage is subtracted from a user's capacity when a work item of this type is assigned. For example, if the Percent Utilization for work item type "X" is set at 25%, a user could receive up to four "X" work items before
the system recognized the user as fully utilized. If the Percent Utilization for work item type "Y" is set at 10%, the user
could receive up to ten "Y" work items before the system recognized the user as fully utilized. This percentage applies to all work items routed to the user, not just the total percentage of a single work item type. For example, if the user received 2 "X" work items and 5 "Y" work items, the system would recognize the user as fully utilized.

Max Assigned

A number, expressed as an integer, which indicates the maximum number of work items of this type that the system will
route to a user with this role. For example, if the Max Assigned setting for work item type "A" is "3," all users with this
role can receive no more than three "A" work items. However, unlike Percent Utilization, the Max Assigned values for a given
work item type do not accrue against other work item types. For example, if the Max Assigned setting for work item "A" is "3" and the Max Assigned for work item "B" is "4," the system does not recognize the user as fully utilized when the user
receives three "A" work items, since the user may also receive up to four "B" work items.