Handbook

Genesys Cloud roles, permissions and divisions: the access control handbook

A detailed handbook for the people who design and run access in Genesys Cloud. It covers the permission catalogue, default and custom roles, divisions, groups, the gaps divisions leave, permission conditions and attribute-based access control, how roles decide licences, OAuth clients, partner access, the 2026 changes and auditing. Checked against Genesys sources on 15 November 2026.

By Dave Tidwell, Managing Director35 min read

In short

  • A role is a bundle of permissions, a grant applies it to a subject, and a division decides which objects it reaches.
  • Guard the Authorization domain: separate role editing from role granting, and keep General > Admin for break-glass only.
  • Divisions protect configuration well and data in flight partly; transfer search, Queue Activity and aggregates stay visible.
  • A role's licence is set by its most expensive permission, and one supervisory permission ends hourly metering.
  • Since 1 June 2026 new permissions are never added to roles automatically unless Role Backfill is on, so review after releases.

01

What access control decides

This handbook is for the people who design and run access in Genesys Cloud: platform owners, administrators, security and data protection leads, and the programme teams who build the first role catalogue. Every statement about what Genesys Cloud does comes from Genesys's own documentation, listed in the sources and checked on 15 November 2026. Access control changed three times in 2026: wildcard permissions ended on 1 June, the permissions view was redesigned on 3 August, and division scoping for authorised-organisation roles arrived on 2 November. Where something is our own practice rather than a Genesys statement, it is labelled QVCCS practice.

1.1 Four jobs in one system

Genesys bases permissions on tasks or job functions, and an administrator assigns them. That single mechanism does four separate jobs, and most access problems come from asking one of them to do another's work.

  • Security and segregation: stopping people seeing or changing what they should not.
  • Commercial: a role determines a licence, and a licence determines a charge (part 11). This surprises people from traditional telephony, where a permission set cost nothing.
  • Data protection: limiting access to recordings, transcripts and personal data, increasingly through attribute-based policies (part 10).
  • Getting people working: agents and supervisors who cannot see the view they need become a go-live defect, when what is missing is one permission.

1.2 The starting point

A user with no role can do almost nothing: until an administrator assigns one or more roles, Genesys says the user or group cannot work in the organisation. The smallest practical permission set is not zero either, because everyone receives the Employee role automatically and it cannot be removed.

Put one warning at the front of every design document. Genesys says to avoid assigning the General > Admin permission, because anyone holding it can create, update or delete anything in the organisation, and to assign it only to essential administrative roles. That is the vendor advising you not to use its own master key.

1.3 Permission, role, grant and division

Each role contains one or more permissions, which let its holders do tasks such as creating groups, setting up integrations or supervising contact centre activity. The chain has four links, and people routinely describe it with three.

  1. Permission: a single named right in the form domain:entity:action, such as authorization:grant:add.
  2. Role: a named bundle of permissions.
  3. Grant: the assignment of a role to a subject, which can be a user, a group or an OAuth client.
  4. Division: the set of objects a grant applies to. The same role granted in two divisions gives two different levels of practical authority.

1.4 Two distinctions that settle arguments

Genesys's key concepts page asks you to understand the difference between a user as an object and a user's permissions. Being able to edit user records is not the same as having the permissions those users hold. It also distinguishes configurable objects, which administrators place in divisions, from transactional objects, which pick up divisions as they move through the system (part 6). Everything above the permission level is yours to design; the permissions themselves are Genesys's, and they change with releases.

02

The permission catalogue: scale and shape

Genesys publishes its full default roles and permissions on one page, the products, roles and permissions list. Its tables load from a script, so they must be read in a browser, and Genesys notes that the list is subject to change. To analyse the catalogue, we counted the permissions attached to the operations in Genesys's published Platform API v2 definition on 15 November 2026. The permission names are Genesys's; the counts, groupings and observations in this part are ours.

2.1 What we counted

The Genesys Cloud permission catalogue, counted from the published API definition (QVCCS count, 15 November 2026)
MeasureResult
Distinct permissions of the form domain:entity:action1,491
Domains (first part)71
Entities (middle part)581
Permissions using view, edit, add or delete1,233 (83%)
Permissions using a capability-specific verb258, across 119 other verbs
API operations in the definition3,303
Operations that accept any one of their permissions2,110
Operations that require all of their permissions842
Operations that declare no permission351
  • These figures are a floor, not a complete catalogue: permissions used only by the interface, or attached to no documented operation, would not appear.
  • They move with releases. Re-count before you quote them.

2.2 The naming is a language, not a list

analytics:conversationDetail:view and recording:recording:view are different permissions with the same last word. When someone says a team needs view access to recordings, the answer is one specific string, and writing it in the role catalogue prevents a long argument later.

Most of the catalogue is create, read, update and delete. The interesting 17% is not: its verbs describe real contact centre capabilities and real privacy risks, including barge, takeover, pauseOthers, monitorAgent, searchAny, viewAll, viewOther and editScreenRecordings. Those are the permissions to review before every audit.

2.3 Some actions need more than one permission

Each operation in the API definition declares whether any one of its listed permissions is enough, or whether all are needed. Creating a division is the clearest example: the operation requires authorization:division:add and authorization:grant:add together. An administrator who can add divisions but not grant roles cannot create one, and the error will not explain why. Genesys documents the same requirement from the other direction: users who move administrative objects need the right divisions on the role that carries the object permissions.

2.4 The largest domains

The 32 domains with ten or more permissions are below, largest first. The other 39 domains hold between one and nine permissions each; 25 of them have fewer than five.

Genesys Cloud permission domains with ten or more permissions (QVCCS count)
DomainPermissionsEntities
wfm17887
outbound13130
conversation9337
routing8228
knowledge7528
externalContacts6120
architect5617
workitems5517
journey5423
analytics4236
recording4113
caseManagement4020
Authorization3613
telephony3517
speechAndTextAnalytics3413
quality316
messaging3013
socialmedia2910
languageUnderstanding289
businessrules276
learning238
chat199
gamification198
assistants197
coaching198
aiStudio177
directory166
presence145
integrations124
webDeployments103
agentic104
responses102

2.5 What the shape tells a role designer

The largest domains carry the most operational risk. Scheduling and dialling dominate, with 178 and 131 permissions, because they touch pay and regulatory compliance; our UK outbound dialling compliance guide covers the second. Some domains are small because they are sharp: Authorization has 36 permissions across 13 entities, but they let a person change what everyone else can do, and realtimeMonitor has five, including screen monitoring. The privacy-related domains, dataprivacy and gdpr, are tiny and matter enormously to a data protection officer.

The small domains are where badly worded access requests end up. A request for access to the voicemail thing is one string among six in the voicemail domain, and the role catalogue should say which.

03

The Authorization domain: the keys to the organisation

If you read one table in this handbook, read this one. The 36 permissions under Authorization are where every privilege escalation path runs. Review them before an audit, before a partner gets access and before an implementation team leaves.

3.1 The 13 entities and their actions

Permissions in the Authorization domain (from Genesys's API definition)
EntityActions
auditview
divisionadd, delete, edit
divisionDeletedview
grantadd, delete, view
licenseview
orgTrusteeadd, delete, edit, view
orgTrusteeClonedUseradd, delete, view
orgTrusteeGroupadd, delete, edit, view
orgTrusteeUseradd, delete, edit, view
orgTrustordelete, view
policyadd, delete, edit, view
roleadd, delete, edit, view
settingsedit, view

3.2 The permissions to watch most closely

  • authorization:grant:add grants a role to a subject, and appears on 18 operations in the API definition, including bulk ones. Combined with the ability to see roles, it lets a person hand out any role in the organisation, including Admin.
  • authorization:role:edit changes what a role contains. Someone holding it can widen a role rather than be granted one, which never shows in a list of role assignments. The Audit Viewer now records these changes (part 13); the question is whether anyone reads it.
  • The orgTrustee permissions let a person authorise users and groups from other organisations into yours (part 12). They are how a partner connection opens.
  • The policy permissions create and edit attribute-based access policies, which can restrict what roles allow (part 10).
  • Outside this domain, directory:organization:admin gates 18 operations in the API definition, including the organisation's authentication settings, IP address authentication and allowlist endpoints, and the authorisation and role settings endpoints.

3.3 Why directory:organization:admin matters

The guardrails described later, Division-Aware Role Management, Role Backfill and Enable Attribute Based Access Control, are all switches on the Organization Settings page. The API evidence suggests whoever holds directory:organization:admin can change organisation-level settings of that kind. Genesys's documentation does not name the permission behind each individual switch, and an interface setting can be gated differently from the public API, so treat the API evidence as a strong indication and test it: in a non-production organisation, give a test account that permission alone and see what it can change.

3.4 A documentation slip to know about

Genesys's procedure for identifying unused roles and permissions tells you at step one to open Menu > User Management > Divisions and then find the role. Roles are listed under Roles and Permissions, not Divisions. The rest of the procedure is correct.

04

Default roles: what a new organisation starts with

Genesys ships a set of default roles. They have quirks that trip up anyone joining an existing organisation, and some of them gate the interfaces people are trained to use.

4.1 Two structural roles

The Employee role has the lowest level of permissions, is assigned automatically to every user added to the organisation, and cannot be removed; to grant more, an administrator assigns additional roles. Admin has permission to make any change to the organisation and is assigned automatically to whoever sets it up. In the context of authorising other organisations' users, Genesys also describes the default Master Admin role as holding every permission needed to administer your organisation. Treat it as a break-glass role, not a daily one.

4.2 Roles that differ by organisation age

The People Admin default role exists only in organisations created after 1 June 2022, so documentation or scripts that assume it will fail quietly in an older organisation. Organisations created before 2020 may still show legacy names: Engage User and PureCloud User for User, Engage Supervisor and PureCloud Supervisor for Supervisor. An access review spreadsheet from a long-standing client that references roles you cannot find is usually showing renamed roles, not deleted ones.

The same page notes that the User role is required to see agent contact centre features, and the Supervisor role to see the Queue and Agent dashboards and reports. Those two are not just job titles; they unlock the screens.

4.3 Feature defaults worth knowing

For some features Genesys documents the default contents directly. The Outbound Agent role includes Outbound > Contact > Edit and View, and Outbound > Dnc > Add: the minimum to work a campaign and honour a do-not-call request. Documents permissions are inherited implicitly: anyone with Admin has the Content Management Admin and User permissions, and anyone with Employee has Content Management User.

One default catches digital-only organisations. Genesys warns that in an organisation licensed for Genesys Cloud 2 Digital or 3 Digital, the Master Admin role includes permissions that enable the full voice licence, so the organisation may be billed for full licences. Its instruction is to remove those voice permissions from Master Admin and give agents the digital agent role, or a custom role without voice permissions.

4.4 Backfill and Restore Default Role

Genesys adds new permissions to default roles through periodic updates. If you customise a default role and later choose Restore Default Role, the permissions you added are lost and those you removed come back. On a live organisation that is a destructive change and deserves the same care as reverting configuration in production.

05

Designing custom roles

Genesys's worked example of a custom role is deliberately small: to let certain managers manage content workspaces and nothing else, create a Content Manager role, add the Content Management Admin permission, and assign it to the people who need it. Its advice on how many roles to build is just as plain.

5.1 Fewer roles, maintained well

Genesys warns that the more roles you have, the longer it takes to manage permissions and the people holding them, and that before creating a role you should consider changing an existing one. Its example: if everyone needs an extra permission such as creating groups, add it to the Employee role rather than create a new role for everyone. Extra roles are for when a subset of people should, or should not, have certain permissions.

Both creation routes exist: add a role from scratch, or copy a similar role and adjust it. Copying is usually better, because it starts from a permission set that works and the result is easier to explain to a reviewer.

5.2 Changes are not instant

Genesys says users see role and permission changes within one to five minutes, and that when you create a group, contact, role or similar object, the user must refresh the list to see it. A user who says it still does not work five minutes after you saved is usually right, and will usually be wrong two minutes later.

5.3 Unused does not mean unnecessary

The Unused column on a role shows that none of the role's holders has needed a permission in the last 30 days. It is not real time: Genesys updates it every 48 hours. Thirty days will not reveal a permission used only at month-end reporting, during a seasonal campaign, or by someone on leave. Remove what is unused in stages, keep the previous definition, and expect a few calls.

06

Divisions: the object model

Genesys describes a division as a way to group and segregate configuration objects while keeping them in the same organisation, for example by business unit, country or office. After creating divisions and assigning objects to them, you use roles to grant users access to divisions, and so to the objects inside them.

6.1 The documented rules

Division limits and rules
RuleDetail
Divisions per organisationUp to 50
Division name lengthUp to 500 characters
Divisions an object can belong toOne at most
Divisions a user can accessNot restricted; a supervisor can hold a role in several divisions
Configurable object types22: call routing objects, coaching appointments, contact lists, data tables, do-not-contact lists, emergencies, extensions, external contacts, flows, flow milestones, flow outcomes, learning modules, management units, message routing objects, outbound campaigns, queues, secondary status, schedules, schedule groups, scripts, users and wrap-up codes

6.2 One object, one division

Genesys's example: a support queue cannot belong to both an East Coast division and a West Coast division. Test that constraint against a real organisation plan before anyone signs off a structure. Two business units sharing one queue cannot both own it; one owns it, and the other gets access through a role granted in that division. People who expect a many-to-many model design the wrong structure and find out at the first cross-brand change request.

6.3 Transactional objects follow the work

This is the most-missed idea in the model. Alongside configurable objects, transactional objects are associated automatically with the divisions they encounter as they move through the system. They include voice, callback, chat, email and message conversations, recordings, presence history and audit data. No administrator files a conversation into a division; it picks up divisions as it passes through queues and agents. That is why access to configuration and access to historical data are separate questions, and why a reporting role that works for queues can still expose recordings.

Once the structure exists, Genesys says ongoing maintenance is minimal: creating a queue is a matter of associating it with the right division.

6.4 Home, All and Unassigned

Every organisation has one Home division, which you can rename and move objects in and out of, but cannot delete. Until you create divisions and organise objects, new configuration objects go to All division and transactional objects are associated with it. Because every object belongs to a division, you never add an existing object to a division; you move it from one to another.

A role can be scoped to one division, several, or all divisions including future ones; holders of the last option automatically get access to every division's resources, including divisions created later. Since 6 December 2023, the first user created when a new organisation is provisioned automatically receives an admin role scoped to all divisions, including future ones. You can edit or revoke it, and on any organisation you inherit, you should check it: a founding account with organisation-wide scope is exactly what a leaver review misses because it looks like a normal admin.

Some resources, including secondary statuses, wrap-up codes, external contacts and external organisations, may be unassigned to any division. Users with the right permissions can then access them regardless of their division assignments.

6.5 New division awareness defaults to visible

The date that explains most division surprises: since 18 October 2023, any resource for which Genesys introduces division awareness is unassigned to a division by default, for backwards compatibility. Genesys's All division page says the same thing: when division awareness reaches a new object type, existing objects stay accessible to all users regardless of their divisions, and you restrict an object by assigning it to a division.

So the rule for an auditor is that division awareness is applied per object, not automatically per object type. A feature that becomes division-aware next quarter will not be hidden from anyone by default.

Genesys also lists 18 configurable types that may not be assignable to All division, including queues, flows, users, schedules and outbound campaigns. Those cannot be placed in All, which is reassuring. The four configurable types not on that list (external contacts, scripts, secondary status and wrap-up codes) are where to check behaviour in your own organisation.

07

Moving objects and Division-Aware Role Management

Moving an object between divisions needs the object's own Edit permission, plus the target divisions on the role that carries it. Genesys's access control permissions page sets out the permissions involved.

7.1 Who can move what

Permissions for moving objects and managing divisions
PermissionAllows
Directory > User > EditMoving members from one division to another
Architect > Flow > EditMoving any flow type between divisions
Outbound > Campaign > EditMoving outbound campaigns between divisions
Outbound > Contact List > EditMoving contact lists between divisions
Outbound > DNC List > EditMoving do-not-contact lists between divisions
Routing > Queue > EditMoving queues between divisions
Workforce Management > Management Unit > EditMoving management units between divisions
Directory > Group > Add and EditCreating and editing groups
Authorization > Division > Add, with GrantAdding a division
Authorization > Division > EditEditing a division's name, description and objects

7.2 Division-Aware Role Management

This setting closes the remaining escalation gap in a divisional design. When it is on, an administrator must hold a role scoped to a division before assigning roles in that division; an administrator whose roles cover only Division A cannot assign roles in Division B. It is a switch in Organization Settings, under Security and Compliance. When it is off, administrators can add or delete role grants for users in any division. Genesys introduced it in July 2023 for exactly this purpose.

Without it, division scoping is advisory: a Division A administrator could grant themselves a Division B role. It is also the answer to a common request, letting team leaders add agents to their own team, which is only safe with this setting on and grant permissions scoped tightly.

7.3 All future divisions

When assigning divisions to a role holder, the All future divisions option removes the need to repeat the step as divisions are added and lets the user move objects immediately. Genesys notes a quirk: you must click Select All before you can tick All future divisions. The option suits a central platform team; it is wrong for a division-scoped team leader.

08

Groups: inherited roles and one important restriction

A group can hold roles, and its members inherit them. Administrators use a group's Roles tab to grant a role to every member and assign divisions to it, which decide what the role can reach. For anything that changes often, group-based assignment is easier to keep correct than assigning roles person by person.

8.1 The inheritance rules

  • When you assign a role to a group, every member gains its permissions, new members inherit them, and a member who leaves the group loses them.
  • Roles inherited from a group cannot be edited in the user's own roles section; the user's record shows which group they came from, and you cannot edit their divisions there.
  • You cannot remove an inherited role from a user except by removing it from the group or removing the user from the group.
  • Genesys's two design rules: to grant a role and its divisions to many people, create a group; to give people with the same role access to different objects, create several groups.

8.2 Role-bearing groups cannot have membership rules

Genesys states that you cannot assign roles to a group with membership rules, and gives the reason as security: the restriction stops rules adding members to a group that would give them permissions nobody specifically granted. If you try to add a role to a rules-based group, you are warned that continuing removes all of its rules.

That is a deliberate design choice: automatic membership cannot be a path to privilege. Groups can still be dynamic, with membership rules based on profile information or relationships, or skill expressions; keep those groups out of the role-bearing set. Where a client wants anyone joining the Leeds team to get the Leeds supervisor role automatically, that belongs in the identity provider and a reviewed assignment process, not in a membership rule.

8.3 The pattern to copy

Genesys's own example is the one we use most. Two outbound contact centres, New York and California, are administered through the same Outbound Admin role, with a different division assigned to that role in each group, so administrators cannot reach any campaigns but their own. One role, two groups, two divisions, and no crossing.

For workforce management, Genesys has since added User Rules for dynamic groupings by business unit, management unit, work team, language, location or reporting line (announced in August 2025, effective December 2025). They are for assignments such as training, not for privilege.

09

Where divisions do not protect you

Divisions are strong on configuration objects and weaker at the edges of the system. Each item below is documented behaviour, and each has appeared in a conversation that began with someone saying they thought divisions did that.

9.1 Seven documented gaps

  1. Transfer targets are not filtered. Genesys states that access control does not limit transfer targets: an agent or supervisor can look up any individual or queue, regardless of division, to transfer an interaction.
  2. Queue Activity shows agents from other divisions. A supervisor cannot open details for users in another division, but their queue membership, presence and conversation details appear in the Queue Activity view. In some sectors, a rival brand's supervisor seeing another brand's agents is a data protection finding.
  3. Queue Agent Details was brought under divisions later: since April 2023, users can view agent information there only if their role is scoped to the agent's division. Genesys's general note that some views show user and queue information regardless of division still applies to the views it names.
  4. Unassigned objects are visible across the organisation (part 6).
  5. Newly division-aware objects default to visible (part 6).
  6. Authorised-organisation roles were organisation-wide until 2 November 2026 (part 12). Check whether existing partner grants were ever scoped.
  7. Licence cost is not divided. Divisions separate access, not spend; a user with one scoped role and one organisation-wide role is billed at the highest licence their roles require (part 11).

9.2 The summary for a design document

Divisions are a strong control over configuration and a partial control over data in flight. Permission conditions and attribute-based policies, in part 10, are the tools for what divisions cannot express, and attribute-based policies are what you add when the data itself is what must be protected.

10

Permission conditions and attribute-based access control

Two layers sit on top of roles and divisions. Permission conditions narrow a specific permission; attribute-based access control (ABAC) evaluates attributes of the user, the resource or the environment, and can only take access away.

10.1 Permission conditions

Genesys lets you narrow some permissions by adding conditions, currently for selected workforce management, analytics, quality and recording permissions. Without conditions, a user with the permission can perform the action; with one or more conditions, the action is limited by them. In the role editor, Add Conditions appears beside permissions that support it.

Genesys's worked example is the case most contact centres need: narrowing the Quality Administrator role. Under Recording, choose the recording permission, add a condition of type Queue, operator Equals, value Support, and that role's access to recordings is restricted to the Support queue.

10.2 The column that explains most surprises

The Edit Role page shows, for each permission, the licence required, whether conditions can be set, whether it is unused, and whether it is Division Aware, meaning it applies only to objects in divisions where the role is granted. If a permission is not division-aware, scoping the role to a division changes nothing for it. That explains a large share of reports that divisions are set up and everything is still visible. Check the column before designing around a permission, not after.

10.3 How ABAC works

Genesys describes ABAC as an authorisation model that evaluates attributes of the subject (the user or entity asking), the object (the resource) or the environment (such as time of day or IP address), working alongside role-based access control and divisions. Policies are Boolean statements evaluated to true or false. Genesys announced it in October 2024 with a planned date of March 2025, and it is now documented as current.

The evaluation order is what to design around. For each resource, Genesys evaluates the ABAC policy first; if it allows access, role permissions and division grants are applied, and both must allow access. ABAC never grants access someone lacks.

10.4 Policy terms and rules

ABAC policy terms
TermMeaning
TargetA specific group of API calls, named like a permission (for example directory:userprofile:edit), usually equating to viewing, editing or deleting a resource
SubjectThe user, group or client the policy applies to; each policy has one subject
EffectAllow or deny. A user who meets an allow policy's conditions, holds the permissions and is not blocked by a deny policy gets access
ScopeGlobal, applying to all API requests, or targeted at a specific domain, entity and action
  • You can have only one policy for a given target and subject; add conditions to the existing policy instead.
  • ABAC is switched on for the organisation in Organization Settings, under Security and Compliance, with Enable Attribute Based Access Control.
  • Policies are created under User Management > Access Policies, from scratch or from Genesys's five templates: Access Control for Gamification Scorecard and Insights, Allow Access from Certain IP Addresses, Allow Only During a Time Frame, Cannot Grant New Roles, and Cannot Update Certain User Profile Fields.
  • Subjects, effect and conditions are defined in the policy JSON, so a policy is an artefact to review like configuration code.

10.5 The templates as a security brief

Read the template names again. Cannot Grant New Roles and Cannot Update Certain User Profile Fields address the two escalation paths that roles and divisions struggle with. Genesys's announcement says as much: ABAC lets supervisors assign agent and supervisor roles without access to higher admin roles, preventing unintended privilege escalation, such as users changing their own role assignments.

10.6 What ABAC covers for conversations

For conversations, ABAC protects conversation records, recordings (including segments, screen recordings and snippets, annotations, retention and deletion protection), transcripts and their summaries and insights, quality evaluations and surveys, and the search experiences and APIs for them. Genesys states that it applies across the interface, public APIs and other supported access points, and that each resource is evaluated separately: access to a conversation does not automatically give access to its recordings.

10.7 What ABAC does not cover

Genesys documents the limits, so design your policies around them.

  • External contacts, Case Management objects and calling lists are not covered; they keep using role and division controls.
  • There is no field-level or partial filtering. ABAC allows or denies a whole resource; it does not redact fields or transcript segments. Masking card numbers in a transcript is a different feature.
  • Search restriction does not evaluate policy expressions; it uses exact matching with contains-all logic.
  • Artefacts are not classified separately. A recording or transcript inherits its access from the parent conversation's attributes.
  • OAuth clients using client credentials carry no user attributes, so policies referring to user attributes treat them as empty. You can exclude such clients and govern them separately (part 12).
  • Orphaned recordings, which have no conversation attributes, are not enforced.
  • Some speech and text analytics data is outside enforcement, including topics and categories detected, sentiment and empathy events, and topic miner snippets; quality calibrations keep using quality permissions.
  • Aggregate reporting, including evaluation and survey aggregates and aggregate performance views, is not restricted by ABAC or search restriction.
  • Existing roles are not redesigned, and ABAC does not manage the lifecycle of the attribute schemas policies depend on.

11

Licences: a role is also a seat

This is the part to share with whoever owns the budget, because it is not how most IT teams expect access control to work. Genesys states that roles are used to manage licences, and that when you assign a role to a user you are also assigning the licence. This part covers that mechanism. For what each Genesys Cloud CX tier includes, see our licence tiers guide; for the overall cost picture, our cost guide. QVCCS sells no licences and quotes no prices.

11.1 The rule that decides the licence

Genesys states that the licence each role uses corresponds to the most expensive permission in the role, and that the licence represents the cost of assigning it. Three behaviours follow, each with a cost consequence.

  • Automatic assignment is the default. Each role has an associated licence reflecting its permissions, and a user's licences update when roles are assigned.
  • One generous permission moves a whole role up. A scheduling role that happens to include a permission needing a higher licence is billed at the higher licence. Genesys shows a Minimum License for each permission on a user's configuration view so you can find it.
  • Under the named model, the user type billed is the highest licence the user held during the billing period. Granting a higher role for a week is not free even if it is revoked.

11.2 Genesys's own examples

Examples of the role-to-licence relationship (from Genesys)
RolePermissionsLicence
EmployeeRead the organisation; edit own profile; edit own locationCollaborate
Telephony AdminConfigure and manage Edge devices; manage phones, numbers and call routingAssociate
Quality EvaluatorView and edit evaluation forms; view an evaluation's audit trail; view and annotate recordings; view a recording's audit trail; create recording encryption keysGenesys Cloud CX 3
  • Read the licence names for your own organisation from the License column on the Edit Role page and the Minimum License column on a user's permissions, and the prices from Genesys's pricing hub or your reseller.
  • Because a role's licence follows its most expensive permission, adding or removing one permission can change it. Check the License column after every role edit.

11.3 Named, concurrent and hourly

Genesys offers named, concurrent and hourly licensing. Under the named model, anyone who logs in during the billing period is a billable named user, however briefly, and logins beyond the purchased number incur overage. Genesys's answer on dormant accounts is useful: users who do not log in during the billing period are not counted. Under the concurrent model, customers are charged for the maximum number of logged-in concurrent users in the billing cycle, disregarding shift-change overlaps shorter than 30 minutes.

Hourly Interacting bills lower-volume users only for the hours they interact. It is set per user through a permission, Billing > User > hourlyInteracting, by way of the Hourly Interacting User role.

11.4 The hourly trap

This is where access control and billing meet most sharply. Genesys states that users with administrative or supervisory permissions are disqualified from hourly metering and moved automatically to full monthly metering under your named or concurrent model, and it publishes a list of the disqualifying permissions. Give an occasional user one supervisory permission and they become a full seat without anyone deciding it. Changing a user's licence type is also retroactive to the start of the current billing period, so a change late in the month is a financial decision as well as an access one.

11.5 Roles enforce the licence model

For Genesys Cloud 2 Digital and 3 Digital, packages that do not include voice, Genesys tells you to give agents the digital agent role or a custom role without voice permissions, and to remove voice permissions from Master Admin (part 4). Genesys Cloud EX, the base licence for workforce engagement on interactions handled elsewhere, requires Collaborate subscriptions as a prerequisite, which Genesys says carry no charge. In each case, the role design is how the licence model is actually enforced.

To reconcile a bill, Genesys documents the self-service route: the Billable Usage or Concurrent Usage report, the licence on the People page (noting that it may have changed during the period), logged-in times in the Agent Status Detail view, or the User Status Detail API.

12

Integrations, OAuth clients and partner access

Everything above applies to software and to other organisations' staff as well as to your own people. These are where the most unreviewed privilege usually sits.

12.1 OAuth clients get roles like people

An OAuth client gets permissions by being granted roles. Genesys's ServiceNow instructions, for example, say to assign the role created for the integration when creating the client credentials client, and they document the role's minimum: all permissions under Conversation and Messaging, plus the integration's own permissions and two message impersonation permissions. Genesys's Salesforce guidance goes the other way, listing permissions per feature so a client can be scoped to what it does.

Since 1 June 2026, selecting all permissions in a domain saves explicit individual permissions rather than a wildcard (part 13). That is better for audit, and it means an integration role will not quietly gain new permissions as Genesys adds them.

12.2 Three behaviours to design around

  • Client credentials have no user context. Genesys explains that roles on such clients have no user context and are not participants in a conversation, so data actions, even those run by an agent from a script, cannot act on conversations. The documented exception: a client with Conversation > Recording > PauseOthers can pause a recording without being a participant. That is why pauseOthers belongs on the review list.
  • ABAC cannot see them as people. Policies that refer to user attributes treat client credentials as empty, and such clients can be excluded and governed separately (part 10). A data protection policy that excludes the largest data consumer needs saying out loud to whoever owns the risk.
  • They can be restricted by IP address. Administrators can set allowed IP addresses for client credentials clients, and ABAC's IP address template is a second route.

12.3 Token lifetime

When creating a client credentials client, you set how long tokens it creates remain valid: a value between 300 and 172,800 seconds, so at most two days. Set it from the integration's real needs, not by accepting the default without thought.

12.4 Authorised organisations

Authorised organisations let you set up a secure relationship with another Genesys Cloud organisation, so permitted users and groups from one can log in to the other. It is how a customer lets a delivery partner in without creating accounts. The host organisation decides what they can do: in a customer-to-partner arrangement, the customer assigns the permissions.

Pairing needs specific permissions: Org Trustee permissions to request a pairing, Org Trustor permissions to approve it, and Org Trustee User and Group permissions, with role view access, to authorise people. Genesys suggests a minimal custom role for managing trusts and authorised users, and notes that customers often give partner users the Master Admin role, granting full admin access, when a custom role would do.

12.5 The November 2026 change

Until 2 November 2026, authorised users and groups received access to all divisions in the roles they were given, and roles assigned through authorised organisations could apply only to all divisions. Now you can restrict an authorised group's roles to specific divisions. On assignment, All Divisions is selected by default; you can remove it and choose specific divisions, but you cannot select other divisions while All Divisions is selected.

A partner connection created before November 2026 is organisation-wide unless someone has changed it. Check it in the first access review after the change.

12.6 Limits and responsibility

Two points belong in a partner agreement. At most 25 users can access another organisation. And Genesys warns that when you grant access to a permitted user or group, you are responsible for how they use your system, and Genesys is not responsible for misuse of data or configuration changes.

There is also a visibility rule for multi-party programmes: only members of the trusted group can see the names of other users and groups in the trust. Others see an empty list with a message about missing permissions, and Genesys does not reveal the trusted group's name to them.

13

The 2026 changes, and auditing access

Three changes in 2026 affect how a role catalogue behaves over time, and the audit tools have improved enough to answer most questions about who changed what. Any internal document written before June 2026 is wrong about the first change.

13.1 Wildcard permissions ended on 1 June 2026

Genesys deprecated the including any future permissions logic behind the All Permissions option, which automatically included new permissions added to a domain or entity, because it could cause unintended billing impacts, particularly when new permissions needed higher licence tiers. Announced on 20 April 2026 and postponed by a month, it took effect with the 1 June 2026 release.

  • All Permissions remains only as a convenience for selecting every permission in a domain or entity; selections are saved as explicit individual permissions.
  • Wildcard permissions were removed from roles and from user permission views.
  • New permissions are not granted automatically to roles, even where All Permissions was selected before. Administrators must assign them.

13.2 Role Backfill: an organisation-level choice

Genesys lets you choose whether it assigns permissions for new features automatically or whether you assign them yourself; the setting is Role Backfill in Organization Settings, available since September 2021. Genesys sets out the trade: automatic backfill removes potentially labour-intensive manual updates, while manual assignment keeps more granular control over access. Since December 2024, the Audit Viewer records system changes made by the backfill process, so switching it on no longer means changes you cannot trace.

13.3 The simplified permissions view, 3 August 2026

Genesys redesigned the permissions layout into a flatter view grouped by domain, with select and deselect at domain level and counters for selected and available permissions. Its stated purpose is to reduce the risk of over-permissioning by making selections more visible. The permission strings have not changed, but every training deck and runbook with a screenshot of the old permissions tab is out of date.

13.4 The Audit Viewer

The Audit Viewer lets you filter and see events Genesys Cloud generates for administrative actions, from a full-page viewer on the Admin page or a mini viewer in the footer of administrative pages. You can search by date range, service, entity type, action, entity ID or user, and each event shows who or what acted, including whether an API or upstream service caused it, the remote IP address, and property values before and after the change. Access needs the Audits > Audit > View permission.

The limit to remember: searches cannot go back more than 14 days. For anything older, Genesys points to the Audit APIs, so a quarterly access review cannot be done in the viewer alone. Since December 2024, the viewer has recorded the permissions administrators, supervisors or Genesys add to or remove from roles, with no configuration needed. Combined with explicit permission storage since June 2026, every change to a role is now attributable.

13.5 What can this person actually do?

The question asked in every incident has a documented answer: open the user under User Management > Users and choose View Permissions. The table lists each permission and the role that grants it, and you can open the role from there. The user's configuration view also shows the minimum licence each permission requires. Most access disputes can be settled on that screen without a meeting.

13.6 Cleaning up

Genesys's stated purpose for the Unused columns is to help you decide which permissions and roles to remove to reduce security risk and lower costs. Because of the 30-day window and 48-hour refresh, remove in stages and keep the previous definition.

14

A starting role catalogue, and what goes wrong

This part puts the handbook to work. The catalogue is our starting point; the failure table is our pattern list. Both rest on the documented behaviours in earlier parts.

14.1 A starting catalogue

The role names, groupings and division advice below are ours, not Genesys recommendations; Genesys's default role list is the authoritative record of what ships. The permission strings are real values from Genesys's API definition, but each selection is a draft to adjust. Write every string out explicitly, check its minimum licence before saving, and fill in the licence consequence from your own role editor.

A starting role catalogue (QVCCS practice)
RolePurposeStart withDivision scope
AgentHandle interactionsThe default User role, then only what is missing, as explicit stringsOwn business unit
SupervisorReal-time views, reports, agent dataThe default User and Supervisor roles, then explicit analytics, queue and recording view strings, and realtimeMonitor view strings onlyOwn units
Quality administratorEvaluations and formsThe quality strings the team needs, plus recording:recording:view with a queue conditionPer brand
Workforce plannerForecasts, schedules, adherenceThe wfm strings for those tasks only, selected deliberately; no Authorization stringsPer business unit
Outbound administratorCampaigns, lists, rule setsThe permissions Genesys lists per outbound roleOne division per operation
Telephony administratorSites, trunks, numbers, phonesThe telephony strings needed, plus routing queue and language stringsUsually central
Flow builderBuild and publish flowsarchitect flow, data table and prompt strings; no telephony or Authorization stringsPer brand
Integration clientOne named integrationThe vendor's documented minimum, listed explicitlyNarrowest possible
Reports consumerRead dashboardsanalytics view strings onlyPer brand
AuditorRead-only oversightAudit view, role view, grant view and division view, plus recording view where agreedAll
People administratorJoiners, leavers, role grantsauthorization:grant:add and grant view, directory:user:edit, and never role:editPer division, with Division-Aware Role Management on
Platform owner (break-glass)Rare emergenciesAdminAll; two named custodians, logged use, quarterly attestation

14.2 Three rules we enforce hardest

  • Separate creating roles from granting them. role:edit and grant:add in the same hands is self-escalation, and ABAC's Cannot Grant New Roles template exists for exactly this.
  • Never grant General > Admin when a scoped set will do; Genesys's own warning is the reason.
  • Every role has a purpose sentence, an owner and a review date. The constraint is not the 50 divisions; it is whether a reviewer can tell what a role is for.

14.3 Ten things that go wrong

Common access control problems, causes and fixes
SymptomLikely causeFix
A new division exists but nobody can add anything to itThe division is not on the role that has the object's Edit permissionAdd the division to the role; give division creators both division:add and grant:add (parts 2 and 7)
A feature that worked in May fails after a releaseA new permission was not granted; wildcards stopped on 1 June 2026Assign it explicitly, or enable Role Backfill with review (part 13)
An agent sees no contact centre screens, or a supervisor no dashboardsThe default User or Supervisor role is missingGrant the default role rather than rebuilding it (part 4)
A role bills at a higher tier than intendedOne permission needs a higher minimum licenceFind it in Minimum License and split the role (part 11)
Occasional users appear as full seatsSupervisory permissions disqualified hourly meteringRemove the permission; remember changes are retroactive in the month (part 11)
A supervisor sees another brand's agents in Queue ActivityDivisions do not filter that viewAccept it or design around it; check Queue Agent Details scoping (part 9)
A division restriction has no effect on a permissionThe permission is not division-awareCheck the Division Aware column on the role (part 10)
Role changes have not taken effectChanges take one to five minutes, and lists need refreshingWait, refresh, then check (part 5)
An inherited role cannot be removed from one userIt comes from a group, by designRemove the user from the group, or the role from the group (part 8)
A partner's admin can reach every divisionAuthorised-organisation roles default to All Divisions, especially pre-November 2026 pairingsRescope each authorised group's roles to specific divisions (part 12)

Questions

Common questions

What is a division in Genesys Cloud?

A division groups configuration objects such as queues, flows, users and campaigns inside one organisation, for example by business unit or country. Each object belongs to one division at most, an organisation can have up to 50, and users reach objects through roles granted in those divisions. Conversations, recordings and other transactional objects pick up divisions as they move through the system.

How does a Genesys Cloud role decide a user's licence?

Genesys states that assigning a role also assigns its licence, and that each role's licence corresponds to the most expensive permission in it. Under the named model, users are billed at the highest licence they held during the billing period. One permission needing a higher licence therefore moves the whole role, and everyone holding it, up a tier.

What changed with All Permissions on 1 June 2026?

Genesys removed the including any future permissions logic. All Permissions now only selects every current permission in a domain or entity, saved as explicit permissions, and wildcards were removed. New permissions are no longer added to roles automatically; administrators assign them, or switch on Role Backfill so Genesys adds them to roles.

Does ABAC replace roles and divisions in Genesys Cloud?

No. Genesys evaluates the ABAC policy first; if it allows access, role permissions and division grants are then applied, and both must allow it. ABAC can only restrict access. For conversations it covers records, recordings, transcripts, evaluations and surveys, but not external contacts, cases, calling lists or aggregate reporting, and it never redacts parts of a resource.

Can supervisors see agents outside their division in Genesys Cloud?

In some views, yes. Genesys documents that transfer search shows any user or queue regardless of division, and that Queue Activity shows queue membership, presence and conversation details for agents in other divisions. Queue Agent Details has been division-controlled since April 2023. Design for these behaviours, and use permission conditions or ABAC where they matter.

How should partner access be controlled in Genesys Cloud?

Use authorised organisations rather than local accounts, and give partners a custom role rather than Master Admin. Since 2 November 2026, roles granted to authorised groups can be scoped to specific divisions; All Divisions is still selected by default, and older pairings are organisation-wide unless changed. At most 25 users can access another organisation.

Sources

  1. Deprecation: Changes to logic in All Permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  2. Deprecation: Outbound Search Audits view – Genesys Cloud Resource Centerhelp.genesys.cloud
  3. Deprecation: Search Audits view – Genesys Cloud Resource Centerhelp.genesys.cloud
  4. Division-based role access for authorized organizations users and groups – Genesys Cloud Resource Centerhelp.genesys.cloud
  5. Introducing enhanced access control with attribute-based policies – Genesys Cloud Resource Centerhelp.genesys.cloud
  6. Restrict OAuth client credentials grants to allowed IP addresses – Genesys Cloud Resource Centerhelp.genesys.cloud
  7. Simplified permissions view in roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  8. Workforce management user rules for dynamic user groupings – Genesys Cloud Resource Centerhelp.genesys.cloud
  9. ABAC for conversations and conversation artifacts overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  10. ABAC policy targets for conversation resources – Genesys Cloud Resource Centerhelp.genesys.cloud
  11. About access control – Genesys Cloud Resource Centerhelp.genesys.cloud
  12. About authorized organizations – Genesys Cloud Resource Centerhelp.genesys.cloud
  13. About groups – Genesys Cloud Resource Centerhelp.genesys.cloud
  14. About people and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  15. Roles and permissions overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  16. About the Audit Viewer – Genesys Cloud Resource Centerhelp.genesys.cloud
  17. Access control overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  18. Access control permissions overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  19. Access control quick start guide – Genesys Cloud Resource Centerhelp.genesys.cloud
  20. Add roles – Genesys Cloud Resource Centerhelp.genesys.cloud
  21. Assign divisions to users from role membership – Genesys Cloud Resource Centerhelp.genesys.cloud
  22. Assign roles, divisions, licenses, and add-ons – Genesys Cloud Resource Centerhelp.genesys.cloud
  23. Assign roles to a group – Genesys Cloud Resource Centerhelp.genesys.cloud
  24. Attribute-based access control overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  25. Authorize users and groups to work in your organization – Genesys Cloud Resource Centerhelp.genesys.cloud
  26. Automatically backfill roles with new permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  27. View a user's permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  28. Configure OAuth client for ServiceNow integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  29. Create access policies – Genesys Cloud Resource Centerhelp.genesys.cloud
  30. Divisions overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  31. Documents roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  32. Edit a role – Genesys Cloud Resource Centerhelp.genesys.cloud
  33. Edit user configuration data – Genesys Cloud Resource Centerhelp.genesys.cloud
  34. Enable attribute based access control – Genesys Cloud Resource Centerhelp.genesys.cloud
  35. Enable division-aware role management – Genesys Cloud Resource Centerhelp.genesys.cloud
  36. Overview of Genesys Cloud 2 Digital and Genesys Cloud 3 Digital licenses – Genesys Cloud Resource Centerhelp.genesys.cloud
  37. Genesys Cloud licenses and billing – Genesys Cloud Resource Centerhelp.genesys.cloud
  38. Genesys Cloud pricing hub – Genesys Cloud Resource Centerhelp.genesys.cloud
  39. Grant a role and a division to a user – Genesys Cloud Resource Centerhelp.genesys.cloud
  40. Hourly licensing model billing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  41. Identify unused roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  42. Key concepts of access control – Genesys Cloud Resource Centerhelp.genesys.cloud
  43. Manage licenses – Genesys Cloud Resource Centerhelp.genesys.cloud
  44. Work with roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  45. Named licensing model billing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  46. OAuth client permissions for Genesys Cloud for Salesforce – Genesys Cloud Resource Centerhelp.genesys.cloud
  47. OAuth client permissions for ServiceNow integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  48. Outbound dialing roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  49. Overview of All division assignment – Genesys Cloud Resource Centerhelp.genesys.cloud
  50. Permission conditions – Genesys Cloud Resource Centerhelp.genesys.cloud
  51. Products, roles, and permissions list – Genesys Cloud Resource Centerhelp.genesys.cloud
  52. Quality management roles and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  53. Roles and permissions for pairing organizations – Genesys Cloud Resource Centerhelp.genesys.cloud
  54. Authorized users and groups roles, divisions, and permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  55. Scope and limitations of ABAC for conversations – Genesys Cloud Resource Centerhelp.genesys.cloud
  56. Scope roles of authorized organizations groups to specific divisions – Genesys Cloud Resource Centerhelp.genesys.cloud
  57. Understand your Genesys Cloud EX subscription – Genesys Cloud Resource Centerhelp.genesys.cloud
  58. View audit events – Genesys Cloud Resource Centerhelp.genesys.cloud
  59. View the users and groups who are authorized to work in your organization – Genesys Cloud Resource Centerhelp.genesys.cloud
  60. Can I use Genesys Cloud data actions to perform actions on conversations? – Genesys Cloud Resource Centerhelp.genesys.cloud
  61. Can we change from a Concurrent or a Named license type to an Hourly Interacting license type? – Genesys Cloud Resource Centerhelp.genesys.cloud
  62. ISV applications FAQs – Genesys Cloud Resource Centerhelp.genesys.cloud
  63. My Queue Activity View shows agents outside of my divisions – Genesys Cloud Resource Centerhelp.genesys.cloud
  64. Our team has several non-active user accounts. We don't want to delete or disable them. Do we still have to pay for them? – Genesys Cloud Resource Centerhelp.genesys.cloud
  65. The Agent Transfer view shows all users (or queues) in the system – Genesys Cloud Resource Centerhelp.genesys.cloud
  66. Why do I see all user and queues data in divisions to which I don't belong? – Genesys Cloud Resource Centerhelp.genesys.cloud
  67. Genesys Cloud licenses and billing – Genesys Cloud Resource Centerhelp.genesys.cloud
  68. configuration objects – Genesys Cloud Resource Centerhelp.genesys.cloud
  69. April 26, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  70. December 2, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  71. July 22, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  72. July 5, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  73. June 1, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  74. May 3, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  75. May 4, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  76. October 18, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  77. September 22, 2021 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  78. Genesys Cloud Platform API v2 definition (permission requirements per operation) – Genesysapi.mypurecloud.com

Last reviewed

We work by introduction

Clients, partners and people introduced to us can reach the right specialist directly.

Who to contact