Access control transactional objects - Genesys Cloud Resource Center
Access control transactional objects
AI-generated summary
Genesys Cloud controls access to call data through a comprehensive division-based and role-based access control system that ensures users only view information relevant to their authorized divisions and organizational roles. The platform assigns divisions to transactional objects including voice, callback, chat, email, message conversations, recordings, presence history, and audit data, with objects receiving multiple division tags when interactions span across different divisions during transfers or consultations. User access is determined by the intersection of assigned roles and divisions, creating a granular permission structure that maintains privacy and compliance while enabling supervisory oversight.
The system implements multi-level access control through three primary mechanisms: division-based permissions that restrict data visibility by organizational unit, recording segment access control that enables selective access to sensitive information, and role-based restrictions that define what each user type can access. Genesys Cloud performs both trunk-side recording, which creates single end-to-end recordings of complete customer interactions accessible to authorized supervisors across divisions, and station-side recording, which captures individual agent perspectives with separate recordings for each participant in transfer, consult, or conference scenarios.
Recording segment permissions enable precise control over sensitive information while maintaining quality assurance and compliance oversight. Only users with the Recording > Recording > View permission can access complete recordings; other users are limited to segment-level access based on role and permission conditions. Access control varies significantly by user role: agents can only access their own segments and screen recordings; supervisors see data based on division access and cannot view segments involving other divisions' agents; and managers with appropriate permissions access all recordings and segments across the organization without segment constraints.
In multi-division interactions, access permissions are strictly enforced based on user participation and authorization. For example, in consult transfer scenarios between divisions, the system creates both trunk-side and station-side recordings segmented into distinct phases including auto-attendant navigation, queue hold, agent pickup, consult initiation, consult conversation, call release, and after-call work. Agents can access only trunk-side segments and station-side recordings corresponding to their participation, supervisors can access recordings from agents within their assigned division including hold music and screen recordings, and managers can access end-to-end recordings across all segments. In blind transfer scenarios between divisions, agents and supervisors retain access only to segments within their respective divisions, preventing unauthorized cross-division access.
Genesys Cloud also controls aggregate data presentation, displaying metrics including skills, DNIS, and wrap-up performance views based on each user's access permissions and granted divisions. Multiple supervisors within an organization can access different divisions, resulting in different metric datasets at the aggregate level. This granular control system ensures that personnel from different divisions cannot access interactions outside their division, maintaining security and compliance while enabling quality assurance and coaching within appropriate organizational boundaries.
In Genesys Cloud, a is a transaction that interacts with or travels through the system. Transactional objects include voice, callback, chat, email, and message conversations; recordings; presence history; and audit data.
Genesys Cloud applies divisions to transactional data to create access control around that data. Each transaction is associated with a division based on objects that the transaction touches during its existence; for example, queues, agents, or call flows. When a transaction connects with or passes through an object, it receives a tag for that object’s division. Transactional objects can associate with more than one division.
Segregation of aggregate data depends on your set-up and how agents transfer interactions, or how transactional data travels through your system. For example, a transactional object connects to two divisions as it travels through the system. If a supervisor has access to only one of those divisions, they can still see the transaction and all related information, including timeline and recordings.
Access control and call recording segments
Genesys Cloud performs trunk-side call recording and creates a single call recording that encompasses what the customer hears during an interaction. This recording includes the transfer path from one agent to another agent or queue, either of which can be associated with another division. In this scenario, a supervisor of either division that has access to the call recording can listen to the end-to-end recording. This access includes the conversation between the first agent and the customer and also the second agent with the customer.
Genesys Cloud also performs station-side call recording which creates a call recording for each agent, captured in the perspective of what that agent hears during the interaction. When an interaction involves multiple internal stakeholders such as in transfer, consult or conference scenarios, multiple call recordings are captured across these agents which can be associated with different divisions. Similarly, a supervisor of either division would have access to all station-side recordings in the interaction.
To prevent supervisors or agents from accessing other divisions’ recording for which they do not have access, implement access control at the recording segment level instead. You can constrain agents and supervisors so that they only hear the segments of the recording that are relevant to them. For more information, see Work with an interaction with recording segment access control.
Access control and aggregate data
In addition to conversation details based on divisions and access control, Genesys Cloud also maintains control over aggregate data. When the system receives aggregate data and metrics, it presents numbers based on conversations associated with the division for which a user has access. If a supervisor can access the skills, DNIS, or wrap-up performance view, the data that appears in those views is based on access control results. Therefore, each user sees the metrics based on the granted permissions and access.
Note: Multiple supervisors in a single organization can access different divisions. Therefore, metrics shown under the skills, DNIS, and wrap-up performance views can display different datasets even at the aggregate level.
Transactional object scenarios
The examples that follow demonstrate the concepts of transactional objects and call recording segments based on access control.
Voice transactional objects
This example describes how the transactional data of a voice interaction travels through the system and connects to multiple divisions. This table describes existing objects, the divisions in which they belong, and the roles that have access to those objects.
Object
Divisions
Roles with access
Main Menu call flow
Corporate
Manager
Support East Queue
Raleigh
Supervisor
Support West Queue
San Francisco
Supervisor
This table illustrates the users and the divisions and roles that have been granted to them:
User
Divisions
Roles granted
Sam
Corporate
Manager
Jesse
Raleigh
Supervisor
Diane
San Francisco
Supervisor
Scenario 1
Call A routes through the Main Menu, which belongs to the Corporate division. Next the call transfers to the Support East queue, which belongs to the Raleigh division, and reaches an agent assigned to that queue. As a result, the voice interaction touches two divisions: Corporate and Raleigh.
Scenario 2
Call B routes through the Main Menu, which belongs to the Corporate division. Next, the call transfers to the Support East queue, which belongs to the Raleigh division. However, the call does not reach an agent, and then transfers to the backup Support West queue, which belongs to the San Francisco division. In this case, the voice interaction touches three divisions: Corporate, Raleigh, and San Francisco.
Access results
Call A touched objects in the Corporate and Raleigh divisions. Call B touched objects in the Corporate, Raleigh, and San Francisco divisions. Therefore, only Sam (with the Manager role and the Corporate division) and Jesse (with the Supervisor role and the Raleigh division) can access Call A data. However, because of the roles and the divisions assigned to those roles, Sam, Jesse, and Diane can all access data for Call B.
Division results based on transactional object
Transactional Object
Division tags
Access
Call A
Corporate
Raleigh
Sam
Jesse
Call B
Corporate
Raleigh
San Francisco
Sam
Jesse
Diane
Access based on user roles and assigned divisions
Role
Division tags
Transactional object
Supervisor
Raleigh
Call A
Supervisor
San Francisco
Call B
Manager
Corporate
Raleigh
San Francisco
Call A
Call B
Not only does Genesys Cloud control access to conversation details based on divisions and access control, it also maintains control over aggregate data. When presented with aggregate data and metrics, the system presents the numbers based on conversations associated with the division for which a user has access. If a supervisor has access to the skills, DNIS or wrap-up performance view, the data presented in these views is based on access control results. Therefore, each user sees the metrics based on the granted permissions and access.
Note: Multiple supervisors in a single organization can access to different divisions. Therefore, metrics shown under the skills, DNIS, and wrap-up performance views may show different datasets even at the aggregate level.
Voice transactional objects and recording segments
For recording segments, we expand on the example in the previous section and introduce Rachel as an agent in Raleigh, and Saurabh as an agent in San Francisco. This table describes the users, the divisions in which they belong, their assigned roles, and the permissions and permission conditions assigned to the role.
User
Division
Role
Permission included in role
Permission conditions
Rachel
Raleigh
User role confined to the Raleigh division
Recording > Recording Segment > View
Recording > Screen Recording > View
Condition Type = User
Operator = Equals
Value = Current User
Jesse
Raleigh
Supervisor role confined to the Raleigh division
Recording > Recording Segment > View
Recording > Screen Recording > View
None
Saurabh
San Francisco
User role confined to the San Francisco division
Recording > Recording Segment > View
Recording > Screen Recording > View
Condition Type = User
Operator = Equals
Value = Current User
Diane
San Francisco
Supervisor role confined to the San Francisco division
Recording > Recording Segment > View
Recording > Screen Recording > View
None
Sam
Corporate
Manager role not confined to a single division
Recording > Recording > View
Recording > Screen Recording > View
None
In this permission setup:
Rachel and Saurabh can only listen to the segments of a recording in which they participate. They cannot listen to other segments of the interaction.
Jesse and Diane can only listen to the segments in which a transactional object within their division participates; for example, a queue, flow, or agent.
Sam can listen to all recordings and does not have segment constraints in any division.
Note: Notice that Sam is the only user with a role that includes the permission Recording > Recording > View for the call media type. Because the remaining users have roles that do not include the Recording > Recording > View permission, they cannot access or listen to the complete recordings.
A customer calls the organization and navigates the IVR prompts in the main menu call flow that is associated with the Corporate division. The call enters the Support East Queue in Raleigh division. Rachel picks up the call and after working with the caller, Rachel ends the call and completes after-call work. Let’s break down the interaction into segments.
Interaction segment
Process
Segment 1
The caller navigates the auto-attendant menu in the Corporate division. Trunk side recording begins at the start of this segment.
Segment 2
The caller enters the Support East queue in the Raleigh division and is placed on hold.
Segment 3
Rachel picks up the call and interacts with the caller. Trunk side recording stops at the end of this segment. Station-side recording at Rachel’s station is captured at this segment.
Segment 4
Rachel ends the call and performs any after-call work.
Access result
Persona
Access
Details
Agent Rachel
Trunk-side call recording
segment 3
Station side recording
Rachel can listen to the segment of the interaction in which she participates. In this case, the time spent on the phone with the caller.
If screen recording is enabled, Rachel can view her screen recording, which begins when she picks up the call.
Supervisor Jesse
Trunk-side call recording segments 2 and 3
Station-side recording
Because Supervisor Jesse and Agent Rachel belong to the Raleigh division, Jesse can listen to Rachel’s segments and hold music.
If screen recording is enabled for Rachel, Jesse can view Rachel’s screen recording.
Agent Saurabh
None
Saurabh does not have access to this interaction.
Supervisor Diane
None
Diane does not have access to this interaction.
Manager Sam
All segments of the trunk-side recording
Station-side recording
Sam can listen to the end-to-end recording.
A customer calls the organization and navigates the IVR prompts in the main menu call flow that is associated with the Corporate division. The call enters the Support East Queue in the Raleigh division. Rachel picks up the call and after briefly interacting with the caller, Rachel starts a blind transfer to send the call to Support West Queue in San Francisco division. She then completes her after-call work. Agent Saurabh picks up the call from the queue, interacts with the customer, and then ends the call and completes his after call work. Let’s break down the interaction into segments.
Interaction segment
Process
Segment 1
The caller navigates the auto-attendant menu in the Corporate division. Trunk side recording begins at the start of this segment.
Segment 2
The caller enters the Support East queue in the Raleigh division and is placed on hold.
Segment 3
Rachel picks up the call, interacts with the caller, and then starts the blind transfer to the Support West queue. Station-side recording at Rachel’s station is captured in this segment.
Segment 4
The caller is placed on hold. Rachel completes any after-call work.
Segment 5
Saurabh picks up the blind transfer and interacts with the caller. Trunk side recording stops at the end of this segment. Station-side recording at Saurabh’s station is captured in this segment.
Segment 6
Saurabh ends the call and completes any after call work.
Access result
Persona
Access
Details
Agent Rachel
Trunk-side call recording
segment 3
Rachel’s station-side recording
Rachel can listen to the segment of the interaction in which she participates. In this case, the time spent on the phone with the caller.
If screen recording is enabled, Rachel can view her screen recording, which begins when she picks up the call.
Supervisor Jesse
Trunk-side call recording.
segments 2 and 3
Rachel’s station-side recording
Supervisor Jesse can listen to Rachel’s segments, and hold music, since they are from Raleigh division.
If screen recording is enabled for Rachel, Jesse can view Rachel’s screen recording. But not Saurabh’s.
Supervisor Jesse cannot access any segments in which Saurabh participates.
Agent Saurabh
Trunk-side call recording segment 5
Saurabh’s station-side recording
Saurabh can listen to the segments of the interaction in which he participates. In this case, the time spent on the phone with the caller.
If screen recording is enabled, Saurabh can view his screen recording.
Saurabh cannot access any segments in which Rachel participates.
Supervisor Diane
Trunk-side call recording
segments 4 and 5
Saurabh’s station side recording
Because Saurabh’s segments and blind-transfer hold music are associated with the San Francisco division, Supervisor Diane can access and listen to them.
If screen recording is enabled for Saurabh, Diane can view Saurabh’s screen recording.
Diane cannot view Rachel’s screen recording or any segments in which Rachel participates.
Manager Sam
All segments of the Trunk-side call recording recording
Rachel’s station side recording
Saurabh’s station side recording
Sam can listen to the end-to-end recording.
A customer calls the organization and navigates the IVR prompts in the main menu call flow that is associated with the Corporate division. The call enters the Support East queue in Raleigh division. Rachel picks up the call and briefly interacts with the caller. Rachel then initiates a consult transfer to Saurabh, which places the caller on hold. Saurabh answers the consult transfer and speaks to Rachel. Rachel releases the call to Saurabh and then completes any after call work. Saurabh interacts with the customer, and then ends the call and completes any after call work.
Note: The consult transfer scenario creates two recordings since trunk’s recording is enabled:
Recording 1: The trunk-side recording that includes the audio content from caller’s perspective. For example, when Rachel initiates the consult transfer, the caller hears hold music.
Recording 2: The audio content from Rachel’s perspective during consult transfer, which ends when Rachel releases the caller.
Let’s break down the interaction into segments.
Interaction segment
Process
Segment 1
The caller navigates the auto-attendant menu in the Corporate division. Trunk side recording begins at the start of this segment.
Segment 2
The caller enters the Support East queue in Raleigh division and is placed on hold..
Segment 3
Rachel picks up the call and interacts with the caller.
Station-side recording at Rachel’s station begins at the start of this segment.
Segment 4
Rachel initiates the consult transfer to Saurabh.
Segment 5
Saurabh picks up the consult transfer and speaks to Rachel. While they interact, the caller remains on hold. Saurabh and Rachel are participants in this segment.
Station-side recording at Saurabh’s station begins at the start of this segment.
Segment 6
Rachel speaks to the caller and then releases the call to the consult transfer.
Station-side recording at Rachel’s station stops at the end of this segment.
Segment 7
Rachel completes the transfer, releasing herself from the call. Rachel completes any after call work. Saurabh interacts with the caller. Trunk side recording stops at the end of this segment.
Station-side recording at Saurabh’s station stops at the end of this segment.
Segment 8
Saurabh ends the call and completes any after call work.
Access result
Persona
Access
Details
Agent Rachel
Trunk-side call recording
segments 3, 4, 5, and 6.
Rachel’s station-side recording
Rachel can listen to the segments of the interaction in which she participates, including the time spent on the phone with the caller.
Rachel can access the consult transfer recording with Saurabh.
If screen recording is enabled, Rachel can view her screen recording, which begins when she picks up the call.
Rachel cannot access any segment of the interaction after she completes the transfer to Saurabh.
Supervisor Jesse
Trunk-side call recording
segments 2, 3, 4, 5, and 6
Rachel’s station-side recording
Supervisor Jesse can access Rachel’s segments, Rachel’s segments that include Saurabh, and both segments of hold music.
Jesse can also access the consult transfer recording between Rachel and Saurabh.
If screen recording is enabled for Rachel, Jesse can view Rachel’s screen recording.
Supervisor Jesse cannot access any segments in which Saurabh participates and Rachel does not.
Agent Saurabh
Trunk-side call recording
segments 5, 6, and 7
Saurabh’s station-side recording
Saurabh can listen to the segments of the interaction in which he participates, including the time spent on the phone with the caller.
Saurabh can also access the consult transfer recording with Rachel.
If screen recording is enabled, Saurabh can view his screen recording, which begins when he picks up the call.
Saurabh cannot access any segment of the interaction prior to receiving the transfer from Rachel, including Rachel’s conversation, and screen recording.