Access control configuration objects

AI-generated summary

Genesys Cloud allows administrators to group configuration objects like queues, flows, and scripts into divisions. Access to view, edit, add, and delete objects can then be granted selectively for each division. This enables access control for different business locations. For example, East Coast and West Coast objects can be put in separate divisions with access granted accordingly. Objects not belonging to a specific division like call flows can go in a "Corporate" division. By default objects are in the Home division which cannot be deleted but can be renamed. The lists the configuration objects that can have access control currently. Key details captured include the ability to group objects into divisions for access control, the default Home division, and the specific objects that can have access controlled

In Genesys Cloud, configuration objects are specific resources within the organization. Administrators can group and associate specific Genesys Cloud configuration objects within a division, and then using access control, selectively grant access to the objects in that division. This access includes view, add, edit, and delete.

If you have two business locations, associate objects specific to those locations. For example, associate objects in an East Coast location in Raleigh and a West Coast location accordingly:

A primary queue for East Coast support, the East Coast office’s call flow menu, and East Coast-based employees that belong to the Raleigh division.
A primary queue for West Coast support, the West Coast office’s call flow menu, and West Coast-based employees that belong to the San Francisco division.
You can also add objects that don’t logically belong to location-based divisions to yet another division, such as Corporate or Customer Care. Here, you can add the company’s primary call flow, marketing or priority support queues, and outbound campaigns.

Note: A configuration object can only belong to one division. By default, all objects belong to the Home division. You can rename the Home division, and you can move objects into and out of it. However, you cannot delete it. You can group objects into the Home division or create new divisions in which to store them. For more information, see .

This table describes the current list of objects for which you can configure access control.

Configuration object	Description
Call routing objects	View, move, edit, and delete call routing objects.
Coaching appointments	View, move, edit, and delete coaching appointments
Contact lists	View, move, edit, and delete outbound dialing contact lists.
Data tables	View, move, edit, and delete data tables.
Do Not Contact lists	View, move, edit, and delete outbound dialing Do Not Contact lists.
Emergencies	View, move, edit, and delete emergency schedules.
Extension assignments	View, move, edit, and delete extension assignments.
Extension pools	View, move, edit, and delete a single extension or a range of extension numbers.
Flows	View, move, edit, and delete specific flows for all flow types in Architect.
Flow milestones	View, move, edit, and delete flow milestones.
Flow outcomes	View, move, edit, and delete flow outcomes.
Learning modules	View, move, edit, and delete learning modules.
Management units	View, move, edit, and delete information in specific workforce management units.
Message routing objects	View, move, edit, and delete message routing objects.
Outbound campaigns	View, move, edit, and delete outbound dialing campaigns.
Queues	View, move, edit, and delete specific queues.
Schedules	View, move, edit, and delete schedules.
Schedule groups	View, move, edit, and delete schedule groups.
Scripts	View, move, edit, and delete scripts.
Users	View, move, edit, and delete data for specific users and agents, including status monitoring, skills, profile, and other person details. Note: A user as a configuration object refers to data about the user. Adding a user to a division does not give that user access to any object data or specific divisions. For more information, see Users as objects vs. users with access in Access control overview.

[NEXT] Was this article helpful?

Get user feedback about articles.

Configuration object

Description

View, move, edit, and delete call routing objects.

View, move, edit, and delete coaching appointments

View, move, edit, and delete outbound dialing contact lists.

View, move, edit, and delete data tables.

View, move, edit, and delete outbound dialing Do Not Contact lists.

View, move, edit, and delete emergency schedules.

View, move, edit, and delete extension assignments.

View, move, edit, and delete a single extension or a range of extension numbers.

View, move, edit, and delete specific flows for all flow types in Architect.

View, move, edit, and delete flow milestones.

View, move, edit, and delete flow outcomes.

View, move, edit, and delete learning modules.

View, move, edit, and delete information in specific workforce management units.

View, move, edit, and delete message routing objects.

View, move, edit, and delete outbound dialing campaigns.

View, move, edit, and delete specific queues.

View, move, edit, and delete schedules.

View, move, edit, and delete schedule groups.

View, move, edit, and delete scripts.

View, move, edit, and delete data for specific users and agents, including status monitoring, skills, profile, and other person details.

Note: A user as a configuration object refers to data about the user. Adding a user to a division does not give that user access to any object data or specific divisions. For more information, see Users as objects vs. users with access in Access control overview.

Access control configuration objects

[NEXT] Was this article helpful?

Loading...

Access control configuration objects

[NEXT] Was this article helpful?