Genesys Cloud - Main

Good day fellow Genesee (?) :)

I believe I know what the answer is to my question, but I still need to ask for peace of mind.

SCIM Azure integration requires the Group visibility set to public. This creates a problem where members of all Divisions can see all the groups and join another division's group chat. (Each division is a country and the customer does not want cross country chat)
Currently, the only option is to disable collaborate chat for the whole Org to prevent agents in different countries from joining group chats that they shouldn't.
This is a problem as we would still like each division's agents to be able to still use group chat.

So the answer to this conundrum is divisional aware groups. Right?

Or is there another way we could 'limit' group chats?

I believe there is something on the roadmap that will address this in some shape or form in the future.

Some confirmation/input from the community will be much appreciated.

Thanks and have a super week,

#ArchitectureandDesign

------------------------------
Dewald Smit
Altron Systems Integration a Division of Altron TMT (Pty) Ltd
------------------------------

Nothing now, but the ABAC stuff coming Q4 or so, should take care of this.  I did add an idea for tracking for the PM:  Add division awareness to chats between | Genesys Cloud Ideas Portal (aha.io)

------------------------------
Robert Wakefield-Carl
TTEC Digital, LLC fka Avtex Solutions, LLC
Contact Center Innovation Architect
https://www.Avtex.com
https://RobertWC.Blogspot.com
------------------------------

Original Message:
Sent: 02-20-2023 07:40
From: Dewald Smit
Subject: SCIM integration, Group Public visibility requirement and Divisions around Collaborate Chat

Good day fellow Genesee (?) :)

I believe I know what the answer is to my question, but I still need to ask for peace of mind.

SCIM Azure integration requires the Group visibility set to public. This creates a problem where members of all Divisions can see all the groups and join another division's group chat. (Each division is a country and the customer does not want cross country chat)
Currently, the only option is to disable collaborate chat for the whole Org to prevent agents in different countries from joining group chats that they shouldn't.
This is a problem as we would still like each division's agents to be able to still use group chat.

So the answer to this conundrum is divisional aware groups. Right?

Or is there another way we could 'limit' group chats?

I believe there is something on the roadmap that will address this in some shape or form in the future.

Some confirmation/input from the community will be much appreciated.

Thanks and have a super week,

#ArchitectureandDesign

------------------------------
Dewald Smit
Altron Systems Integration a Division of Altron TMT (Pty) Ltd
------------------------------