Genesys Cloud – ABAC bypass setting for Genesys Services
In a future release, Genesys Cloud will introduce an organization-level setting that allows administrators to control whether paired Genesys Services teams, such as Genesys Cloud Customer Care, and access requests from Genesys IP ranges can bypass attribute-based access control (ABAC) global policy conditions. The setting will be enabled by default. When enabled, Genesys Cloud will skip ABAC enforcement for these access requests. When disabled, the organization’s ABAC policies will apply to Genesys Services and Genesys IP ranges.
What’s changing
- Genesys Services access – Administrators can allow paired Genesys Services teams to access their organization when ABAC conditions, such as IP range or time-of-day restrictions, would otherwise prevent access.
- Genesys IP range access – When the setting is enabled, Genesys Cloud will skip ABAC enforcement checks for access requests from Genesys IP ranges. Administrators can retrieve the list of Genesys IP ranges associated with this setting through the IP ranges API.
- Administrator control – Administrators can disable the setting when they want their ABAC policies to apply to Genesys Services and Genesys IP ranges.
- Default behavior – The setting will be enabled by default to preserve the support access model available with the Allowed IP Addresses feature.
- CX as Code support – Administrators can also manage the setting through Terraform.
Why this matters
ABAC global policies can restrict access to a Genesys Cloud organization based on environmental attributes such as IP range or time of day. Those restrictions can also prevent authorized Genesys Services teams from accessing an organization to investigate customer-reported issues. The new setting gives administrators a targeted way to allow approved Genesys access without requiring them to maintain Genesys IP ranges and other access conditions in their ABAC policies or disable ABAC protections for other users.
Action required
No action is required. The setting will be enabled by default. Administrators who want ABAC policies to apply to paired Genesys Services teams and Genesys IP ranges can disable the setting and configure their ABAC policies accordingly.
[NEXT] Was this article helpful?
Get user feedback about articles.