Genesys Cloud – Deprecation: Changes to logic in All Permissions
| Announced on (YYYY-MM-DD) | Effective date (YYYY-MM-DD) | Aha! idea |
|---|---|---|
| 2026-04-20 | 2026-06-01 | - |
Genesys Cloud is deprecating the including any future permissions logic associated with the All Permissions option. This logic automatically includes any new permissions added within a domain or an entity, and may lead to unintended billing impacts, particularly when new permissions require higher license tiers.
As part of this deprecation, on the effective date:
- The including any future permissions logic will be removed.
- The All Permissions option will remain, however:
- It will function only as a selection convenience tool to select all permissions in a domain or entity.
- Permissions will be saved as explicit individual permissions, not as wildcards.
- Wildcard permissions (*) will be removed from:
- Roles
- Individual user permissions views
- When new permissions are introduced:
- They will not be automatically granted to the roles, even if the All Permissions option was previously selected.
- Administrators must manually assign new permissions, if necessary.
- Existing roles that use wildcard permissions will be automatically refreshed to expand to explicit permissions.
Also, API responses will be updated so that wildcard permissions are expanded into explicit permissions rather than returned as wildcard entries.
FAQs
Am I affected?
You are impacted if your organization:
- Uses the All Permissions option in Roles and Permissions.
- Relies on automatic inclusion of newly added permissions.
- Uses or interacts with wildcard permissions (*) in roles or API responses.
- Uses the following API for bulk-granting subjects and divisions with an organization role.
post /api/v2/authorization/roles/{roleId}
What do I need to do before the removal date?
No immediate action is required. These changes are automatically applied.
If you rely on API responses containing wildcard permissions, ensure that your integrations can handle explicit permission lists instead.
How can I prepare for this deprecation?
After this change takes effect, if new permissions are introduced and you want them included in a role, you must manually update the role to add those permissions.
You may want to:
- Review roles that currently rely on All Permissions.
- Establish a process to review periodically and update roles when new permissions are introduced.
What if I need help or have questions?
Contact your Genesys account team. You can also visit Genesys Product Support for more assistance.
[NEXT] Was this article helpful?
Get user feedback about articles.