Handbook

Genesys Cloud user lifecycle: the handbook for SCIM, SSO, MFA and licences

A detailed handbook for the people who run users in Genesys Cloud. It covers how people arrive, CSV import rules, SCIM provisioning and its traps by identity provider, invitations and user states, what deletion leaves behind, SSO and its certificates, MFA and passwords, and the licence and add-on effects of everyday changes. Checked against Genesys sources on 15 November 2026.

By Dave Tidwell, Managing Director31 min read

In short

  • Identity, access and licence are separate jobs, but in Genesys Cloud the licence follows the roles you grant.
  • SCIM is one-way: fix data upstream, build divisions before mapping them, and put roles on directory-managed groups.
  • Deleting a user keeps their history and email; erasure is a separate, per-person GDPR request.
  • Genesys Cloud MFA and password rules protect native logins only; SSO users get their second factor from the provider.
  • Watch the hourly disqualifying list, WEM triggers and overage, and reconcile the directory with Genesys Cloud monthly.

01

What you are operating

This handbook is for the people who run the user lifecycle in Genesys Cloud: identity and directory teams, Genesys Cloud administrators, service desks and the finance colleagues who receive the invoice. It covers how people arrive, SCIM provisioning, SSO, MFA and passwords, user states and deletion, and the operational side of licences. Every statement about what Genesys Cloud does comes from Genesys's documentation, listed in the sources and checked on 15 November 2026. Where something is our own practice rather than a Genesys statement, it is labelled QVCCS practice. Our roles and permissions handbook covers the access model this lifecycle operates.

1.1 Three operations usually called one

Identity is who a person is and how they prove it: email address, SSO assertion, MFA device and directory record. Access is what they may do: roles, divisions, conditions and policies, downstream of identity. Licence is what they cost, and in Genesys Cloud it is not a separate step after access but a consequence of it. Genesys states that assigning a role also assigns its licence, and that each role's licence follows the most expensive permission in it. A joiner, mover and leaver process written without that coupling produces correct access and wrong bills.

1.2 Billing follows login, not existence

Under named licensing, anyone who logs in during the billing period is a billable named user, however briefly. Genesys's answer on dormant accounts is equally clear: users who do not log in during the billing period are not counted. So the leaver process is a security control and a cost control, and its timing is measured in logins.

A user is also a long-lived object whose history outlives them. Deleting someone removes their permissions and stops them logging in, but Genesys does not delete some related information, including their email address, performance data, conversation and chat history, documents and voicemails (part 7).

1.3 The user record: five things that must be right

The five elements of a Genesys Cloud user record
ElementWhat it isWhat goes wrong
IdentityEmail address, plus SSO provider, or password and MFA devices for native loginThe SSO assertion's email does not match the record, so the user cannot log in at all (part 8)
ProfileName, title, department, manager, location, phone, hire dateA directory field nobody mapped, so manager filters and management unit logic quietly fail
Roles and divisionsWhat they may do, and to which objectsRoles not restored after re-enabling a deleted user (part 5)
LicenceDerived from roles and shown as the licence typeA harmless-looking role change moves the licence tier (part 11)
StateActive, inactive or deletedEach party meant something different by deactivated, so billing continues or history goes (parts 6 and 7)
  • The People page filters by name or email, group, role, location, division, reports-to and status (active, inactive or deleted), and supports bulk state changes, invitations and skills. The reports-to and division filters turn a review into a query rather than a scroll.
  • Accounts can be created before users are allowed to log in, which helps with large waves: a created but uninvited user has not logged in, so is not billable.
  • Genesys's documentation does not state a maximum number of users per organisation; if a contract needs one, it comes from Genesys.

02

How people arrive, and CSV import

Genesys lists three ways to add people: synchronise from an identity management system using Genesys Cloud SCIM, import a CSV file of basic profile information, or add people individually. They suit different jobs, and mixing them carelessly is where records go wrong.

2.1 Choosing a method

Ways to add people to Genesys Cloud
MethodBest forMain risk
Add a personOne-off joiners, test accountsUndocumented drift: an account that no process created
CSV importCutover waves, migrations, organisations without a managed directorySilent overwrites and duplicate roles (2.3)
SCIMOrganisations using Microsoft Entra ID, Okta or OneLoginThe one-way rule, and mappings nobody retests (parts 3 to 5)

2.2 The CSV format

Genesys recommends exporting the file from a spreadsheet rather than writing it in a text editor, because the spreadsheet inserts the quotes and commas correctly. The columns must appear in a fixed order: name, email, phone_work, extension, title, department, email_manager, location_work, roles_divisions, queues, division, skills and hire_date. Only name and email are required. Roles must be spelled exactly as they appear on the Roles/Permissions page, and the skills column accepts skills, not languages. Files containing languages such as Japanese or Chinese must be saved as Unicode or UTF-8.

2.3 The overwrite rules are asymmetric

This is the most important part of the CSV route. If the extension, title or department columns are empty, the blank fields override existing values in Genesys Cloud. If phone_work, email_manager, location_work, roles_divisions, queues, division or skills are empty, existing values are kept. Three columns are destructive when blank; seven are safe. A file built by copying a subset of columns, or with gaps from filtering, will erase job titles and departments across an organisation.

Updates add roles and queues but never replace or remove them, so a CSV import cannot take access away. Skills are the exception that inverts the rule: new skills in the file replace existing ones, with proficiency written inline, such as Skill1:5,Skill2:3. In the same file, one column adds and the next replaces.

2.4 Four smaller traps

  • Validation does not catch spelling errors or extra spaces, which Genesys warns can create duplicate roles. A trailing space after Supervisor creates a second role.
  • Queue names are comma-separated in one field, so a queue name cannot contain a comma.
  • New locations in the file are added to the organisation automatically, so a typo becomes a permanent location.
  • Update Existing People and Send Invitation Notification are separate choices. Inviting 400 agents at nine on a Monday morning is a support event; decide deliberately.

03

SCIM: what it syncs, and the one-way rule

Genesys Cloud SCIM uses SCIM APIs to sync users from cloud or on-premises identity management systems into Genesys Cloud. Genesys lists Microsoft Entra ID, Okta and OneLogin as supported. One sentence from Genesys belongs in every design document and handover: Genesys Cloud currently supports only one-way syncing from the identity system to Genesys Cloud, and changes made in Genesys Cloud are not synced back and may be overwritten.

3.1 Three consequences of one-way sync

  • Genesys Cloud is not the system of record for profile data. Editing a job title, department or phone number there is temporary.
  • The next sync can undo a deliberate change. If an administrator corrects a manager field because the HR record is wrong, provisioning puts it back. The fix is always upstream, and the route to whoever owns the directory must be written down before go-live.
  • Where CSV and SCIM touch the same records, the last writer wins on mapped attributes. One system of record prevents it.

3.2 What provisioning can do

For Microsoft Entra ID, Genesys states that provisioning can create, update and delete users, and can add users to or remove them from public groups, but cannot create or delete groups. For Okta, the supported features are Create Users, Update User Attributes, Deactivate Users, Sync Password and Push Groups. Both lists include privileged capabilities: removing access and granting it through groups.

3.3 The setup credential

The Entra ID configuration is completed with a bearer token obtained through the Genesys Cloud API, entered with a tenant URL ending in /api/v2/scim/v2/ on your region's API domain, for example api.euw2.pure.cloud for the London region. That token is a long-lived machine credential, not a person's password. Put it on the secrets register with an owner and a review date, and revoke and replace it when the person who set up provisioning leaves.

04

SCIM field mappings and their traps

The mapping table decides what Genesys Cloud's data quality will be for years. Genesys ships defaults you can edit; the ones worth knowing are those that create identity.

4.1 The key Entra ID mappings

Key default Entra ID to Genesys Cloud SCIM mappings
Entra ID attributeSCIM fieldEffect in Genesys Cloud
userPrincipalNameuserName (required)Generates the user's main email address in Genesys Cloud
Not([IsSoftDeleted])active (required)Drives active or inactive state
displayNamedisplayName (required)The user's name
jobTitletitleJob title
managerenterprise manager valueReporting line
departmententerprise departmentDepartment
Customer-chosen fieldenterprise divisionDivision, which must already exist (4.2)
StripSpaces([telephoneNumber])work phone numberPhone, with documented extension options
  • On the Genesys side, userName maps to the user's main email, and the enterprise extension carries department, manager, hire date (returned as YYYY-MM-DD) and division.
  • Extensions have documented expression mappings too: extension only, or a tel: value with the extension appended.

4.2 The division field does not create a division

Genesys is explicit: the division field maps to the Genesys Cloud division ID and does not create a division. It must match the name of an existing division or be blank, and when none is given the user goes to the Home division. Divisions are therefore a two-step job: build them in Genesys Cloud first, then feed names that match exactly. A typo sends people to Home, and the problem appears later as a supervisor who cannot see their own queue. Agree the division naming standard in discovery, before anyone builds a mapping.

4.3 You cannot clear a field by blanking it upstream

Genesys warns that with Entra ID, trying to clear a previously synced field by mapping it to an empty value does not work, because Microsoft's sync ignores empty values and leaves the original data in place. With the one-way rule, wrong data becomes sticky: it will not clear by going empty at the source, and fixing it in Genesys Cloud will be overwritten. The reliable routes are a deliberate non-empty value upstream, or an administrator edit plus a mapping change.

4.4 Phone formats can cause endless updates

Genesys warns about this twice. With Okta, Genesys Cloud converts phone numbers to E.164 format, so if Okta pulls back numbers in a different format the result is continual updates; the fix is to hold numbers in E.164 in Okta. With Entra ID, map phones through StripSpaces([telephoneNumber]) so they match Genesys Cloud's format and do not trigger needless updates. The symptom is a provisioning log full of the same users updating forever.

4.5 Pilot first, and mind other integrations

Genesys recommends a pilot with a small subset of users to check configuration and mappings, noting that corrections may need manual adjustment of the synced test users. In other words, there is no clean rollback for a mapping that wrote bad data to thousands of people: pilot with a few dozen, field by field.

If you use the Microsoft Teams integration alongside SCIM, extra mappings are needed for the Teams badge, external presence and click-to-dial. Genesys's unified communications guidance adds that only one UC phone integration can be enabled per user.

05

SCIM joiners, movers and leavers by provider

This part decides whether your leaver process works, and the behaviour differs by identity provider. Genesys documents each.

5.1 Microsoft Entra ID

If you remove a user from the app's scope or soft-delete them in Entra ID, Entra ID tells Genesys Cloud to make the user inactive. When the user is hard-deleted, either by you or by Entra ID's maintenance schedule (currently 30 days after removal or soft deletion), Entra ID tells Genesys Cloud to delete them.

Two things follow. The deletion date in Genesys Cloud is set by Microsoft's schedule, not your process, so it will not match a records team's expectations. And a leaver is inactive, not deleted, for about a month: normally what you want, with history intact and no licence running, provided the process says so explicitly.

5.2 Okta: unassigning a user

When you unassign a user from the Genesys Cloud application in Okta, the user becomes inactive and keeps their roles if reactivated. Inactive and deleted users both lose access. Genesys recommends deleting inactive users in Genesys Cloud to complete the process: the identity provider's step is not the whole job.

5.3 Okta: delete, then re-enable

This is the most common seasonal workforce defect. If you delete a user in Genesys Cloud and later re-enable them in Okta, they become active again, but unlike a new user, Genesys Cloud does not restore the default Employee role or any manually added roles. You must reassign roles or use Push Groups, and Genesys recommends assigning roles to a group in Genesys Cloud and adding the user to the group in Okta.

Delete leavers to keep things tidy, rehire a returning summer agent, and they arrive active with no roles at all. They can log in and see nothing. The fix is Genesys's own recommendation: put roles on groups and let the directory manage membership, so a rejoiner gets their roles back the moment they are added to the group.

5.4 Movers and unexpected changes

In Entra ID, a mover is a scope or group change upstream. In Okta, later attribute changes in the user's profile automatically replace the matching values in Genesys Cloud, which is the one-way rule in action.

Genesys also documents a residual risk: occasionally, when Microsoft updates Entra ID, it also updates the Genesys Cloud provisioning app, which can make unexpected changes to user records and sometimes stop users working. The documented investigation route is Microsoft's audit and provisioning logs, then Genesys Cloud's audit log viewer and its catalogue of audited actions. The fix is to correct the mappings and intervene manually once they are back to the desired state.

5.5 SCIM and groups: four constraints

  1. Groups must be public, and names must match in both systems, ignoring case; otherwise Entra ID cannot sync membership. A private group is simply not synced.
  2. Provisioning cannot create or delete groups in Genesys Cloud, only change membership. The group must exist first, with its role already assigned.
  3. When syncing groups, select only Update; create and delete are not supported for groups.
  4. Genesys Cloud does not allow roles on a group with membership rules, so that rules cannot add people to a group that grants permissions nobody specifically approved.

06

Invitations, first login and user states

An account is not usable until it is invited and someone logs in. Once in use, its state decides whether it can log in and therefore whether it costs anything.

6.1 Invitations and the first login

Invitations are separate from account creation. You can invite one person from their record, or use Send Invites to email everyone who has neither received an invitation nor logged in. At first login, native users set a password and can set up MFA from My Account, holding up to five MFA devices. Genesys warns not to paste passwords containing double-byte characters, such as Japanese or Chinese characters, because the user cannot then type them at the keyboard.

SSO changes the first login. Users choose More Login Options, enter the organisation name, select the region and click the identity provider icon; after that, they log in from the provider icon directly.

6.2 Two details that generate tickets

If a user forgets their password and uses the same email address in more than one organisation, they must also enter the organisation name when resetting it, with a Forgot Organization Name link to help. And the browser extensions have an Auto Redirect to SSO setting that takes the identity provider name and the organisation's short name; Genesys says the capitalisation must match the short name exactly. Put that value in the build script, not in a runbook someone types from.

6.3 Active, inactive and deleted

Genesys's Set State control moves users between active, inactive and deleted, and notes that active users can log in, which affects billing, while inactive users cannot. It recommends inactive for seasonal workers or people on extended leave who plan to return, and notes that both deletion and inactivation can be used to track attrition.

What each user state means in practice
StateCan log inRolesBillableUse for
ActiveYesKeptOnly if they log in during the periodPeople working now
InactiveNoKept, and restored on reactivationNo, provided they cannot log inSeasonal staff, extended leave, suspensions
DeletedNoPermissions removed; not restored when re-enabled through SCIMNoPeople who have left permanently

6.4 Inactive is the pause button

Because billing follows login, an inactive account costs nothing, but only if the person truly cannot log in. That is why directory status and SSO scope matter as much as the Genesys Cloud state: an account inactive in Genesys Cloud but still assigned in the identity provider, with native login still possible, is a surprise waiting to happen.

Concurrent licensing sharpens this. Genesys charges for the maximum number of logged-in concurrent users in the billing cycle, ignoring shift-change overlaps under 30 minutes, so an unexpected peak is what you pay for all month.

07

Leavers: what deletion does not do

Deletion is the most misunderstood operation in Genesys Cloud administration. Delete does not mean delete.

7.1 What deletion does and does not do

When you delete someone, Genesys Cloud deactivates the account so they can no longer log in and removes all their permissions. They disappear from directory search and others cannot see their profile.

Genesys does not delete some related information, including the email address, performance data, conversation history, chat history, files in documents and voicemails; that data can be removed through the GDPR API. Active users may still see the deleted user in their chat roster, marked as inactive, and can still read chat history with them.

7.2 Three further consequences

  • A user in a custom division at deletion moves to the Home division, and stays there if restored until someone moves them back. With roles not restored on re-enable, a restored user can be active, role-less and in Home, which looks like a broken organisation.
  • An account deleted through the GDPR API cannot be undeleted. The two deletion routes differ in reversibility; choose deliberately.
  • Because of retained data, Genesys does not recommend reusing a deleted account or email address.

7.3 Data subject requests are a different job

Genesys's GDPR API maps request types to GDPR articles: Export to Article 15 (access), Update to Article 16 (rectification) and Delete to Article 17 (erasure), noting that for Delete some services may anonymise personal data rather than delete it. Each request takes one search term; Genesys advises checking first that the term matches only the intended person, then submitting requests for every identifier known for them.

The warning for whoever owns privacy operations: Genesys states that the GDPR API is not designed for bulk requests such as bulk deletion, and bulk requests may be cancelled because of potential platform instability. A clean-up script that erases thousands of former employees is exactly what gets cancelled, possibly part-way through.

08

Single sign-on: configuration and identity matching

With SSO, users sign in through their identity provider rather than a Genesys Cloud password. Genesys Cloud is the service provider in a SAML relationship, and the configuration is symmetric: you give Genesys Cloud the provider's metadata, and the provider receives Genesys Cloud's.

8.1 Exchanging metadata

On saving an SSO configuration, Genesys Cloud generates the SAML metadata your identity provider needs, including the Issuer URI, Assertion Consumer Service and Single Logout URI, available through Download Metadata, or the certificate alone through Download Certificate. In the other direction, importing the provider's metadata file fills in the required fields and the public X.509 certificate for signature validation. Import metadata rather than transcribing URLs by hand.

8.2 Facts that shape an SSO design

Single sign-on limits and behaviours
FactDetail
SSO integrations per organisationUp to 30, of the same provider or a mix
Login page logoSVG format, at most 25 KB
Display names on the login pageNot available with more than six identity providers
SAML attributesCase-sensitive
Assertion encryptionSupported: give the provider the Genesys encryption certificate
CertificatesUp to five per SSO configuration, with expiry shown on the Single Sign-On page
  • The AuthorizedClientIDs attribute lets the identity provider list the OAuth client IDs a user may access; if the user tries another, Genesys Cloud sends them back to SSO to reauthenticate instead of issuing a token.
  • Another attribute sets where the browser lands after sign-in. Copy attribute names from Genesys's table rather than typing them, because they are case-sensitive.

8.3 The matching rule

The user's SSO email address must match the email configured for that user in Genesys Cloud. A mismatch is the commonest cause of a total SSO failure that looks like a configuration error. Under SCIM that email comes from the user principal name mapping, so if a client renames user principal names after go-live, assertion and record diverge.

Organisations that cannot match on email have an answer: since December 2022, administrators can let users log in with an identifier other than an email address, documented in Genesys's guide to configuring an SSO identity provider without an email address. For alias domains or shared mailboxes, decide this before go-live.

8.4 Several identity providers

With two or more SAML identity providers configured, users choose one on the login screen; Genesys's example has three providers side by side, and a generic provider can sit alongside named ones. This suits acquired companies, franchises and separate legal entities with their own directories. Design the login page so users recognise their own provider, with a login name and logo for each, remembering that display names disappear above six providers.

Genesys gives a useful diagnostic: if the identity provider link does not appear on the login page, something in the configuration is wrong. A missing icon is a configuration problem, not a user problem.

09

SSO certificates and SSO-only login

Two SSO operations cause most of the outages we are asked about: a signing certificate that expired unnoticed, and an integration that stopped working when native login was switched off.

9.1 Certificate rotation is a recurring cliff

Genesys rotates its SSO signing certificate, and the last rotation is the template for the next. The previous certificate expired on 1 January 2026; the new one was downloadable from 2 November 2025 and became active on 10 December 2025, a date Genesys chose to minimise disruption over the holidays.

You were affected if you sign authentication requests, or use Single Logout with an identity provider that verifies Single Logout signatures. Both are visible in the Single Sign-on settings. The action was to give the identity provider the new certificate: any time after 2 November if it supports several certificates, otherwise on or after 10 December.

9.2 Rotations are timed by region

Genesys published a schedule by region. For London and Ireland the change ran at 4 pm US Eastern, 9 pm local time, with other European and African regions later in their evenings. A contact centre that runs across time zones cannot treat a rotation as out of hours, because for some sites it falls in their working day.

9.3 SSO-only login

Administrators can disable Genesys Cloud's own login so that users must sign in through a selected identity provider, a capability since February 2019. It is a single setting under Organization Settings, Authentication, Disable Genesys Cloud Login, with a confirmation prompt.

  • All password requirement settings are disabled, because Genesys Cloud authentication is no longer used, but they are preserved in case native login is switched back on.
  • Administrators cannot delete every SSO provider while native login is disabled, which protects against locking the organisation out.
  • Users must sign in through SSO and are asked which provider to use.

9.4 The integration SSO-only breaks

Genesys warns: do not enable SSO-only authentication if you use webhooks for chat notification integrations, because that feature needs password-based authentication and fails when SSO-only is on. That is a trap with a long fuse: a webhook built in year one works until the security team enforces SSO-only in year two, and the failure gives no hint that authentication is the cause.

10

MFA and passwords

Genesys Cloud's own multi-factor authentication and password policy matter, but for a narrower population than many security reviews assume.

10.1 MFA is for native login only

Genesys states that it supports MFA for native login only, and that SSO users do not receive MFA prompts. That one sentence settles a common and costly misunderstanding: once SSO is in place, Genesys Cloud MFA is not the organisation's MFA strategy. The second factor for SSO users is enforced by the identity provider, and the assurance evidence has to come from there.

10.2 What Genesys Cloud MFA does

  • Organisation-wide enforcement, through Require Multi-Factor Authentication under Organization Settings, Authentication. Enabling it needs, among others, the Directory > Organization > Admin permission.
  • Turning the requirement off does not remove anyone's second factor: Genesys notes that users can still set up MFA themselves, and once configured it is enforced.
  • Users with specific administrative permissions must use a second factor regardless of the organisation setting.
  • Methods include authenticator apps using time-based one-time passwords and passkeys, with up to five MFA devices per user. Since 15 December 2025 users can also register built-in authenticators such as fingerprint readers and security keys, for native login only.
  • Since January 2026, users with several devices can choose which one Genesys Cloud asks for first.

10.3 Plan resets before enforcing

Genesys's own prerequisite for enabling MFA for everyone is that administrators hold the permissions to reset MFA devices. Resetting a device is the most common identity call in a native-login estate, so the permission and an identity-verified reset procedure must exist before the setting is switched on; otherwise the first lost phone becomes an outage at the start of a shift.

10.4 Password policy

Genesys's default rules: at least eight and at most 400 characters; at least one number, one special character, one uppercase and one lowercase letter; and no reuse of the previous ten passwords. Administrators can set different minimums and maximums. These became Genesys's minimum policy in December 2023, and three points from that change matter to security architects: organisations did not need to update their policy to meet it; users had to change passwords only when next required; and SSO users were not affected. Organisations that set or reset passwords through automation had to make sure their scripts complied.

Self-service reset is available from the login page, with a link sent by email and an MFA challenge afterwards if the organisation requires it.

10.5 What to tell an auditor

In a mature estate, Genesys Cloud's password policy and MFA protect a shrinking population: break-glass accounts, native-login service paths and anything not yet on SSO. They should exist and be strict, but they should not be described as the organisation's identity control, because that control sits with the identity provider.

11

Licences in day-to-day operation

Our roles and permissions handbook explains how roles decide licences. This part covers what that means for the people running joiners, movers and leavers, and for whoever reconciles the bill. QVCCS sells no licences and quotes no prices; rates come from Genesys or your reseller.

11.1 Where to see the licence, before and after a change

Assignment is automatic by default: each role has an associated licence, and a user's licences update when roles are assigned. Three views make up the whole of a pre-change impact check. On the user, the Division and License panel shows the licence type and available add-ons. On the user's permissions, the Minimum License column shows the lowest licence each permission needs. On the role, the License column shows what the role requires.

11.2 A worked example

A client asks for team leaders to see a detailed analytics view. An administrator finds the analytics permission behind it, adds it to the existing Team Leader role and saves. If that permission needs a higher licence, every holder of the role moves up a tier, not just the person who asked, and nobody sees it until the invoice. The controls are simple: read the role's License column before saving, check Minimum License for the permission being added, and treat any role edit that changes the displayed licence as a change request.

11.3 Short-term peaks need no contract change

Genesys explains that increasing your annually committed seats is done through your client success or sales representative, and that if the increase is only for a few months, no action is needed: usage above the commitment is billed at the overage or month-to-month rates in your contract. A seasonal peak needs a decision about accepting overage, not a contract amendment.

11.4 Licence models

Genesys Cloud user licence models
ModelCounted asKey rules
NamedEach user who logs in during the periodBilled however briefly logged in, at the highest licence held during the period; overage above the purchased number
ConcurrentThe peak number of logged-in concurrent usersShift-change overlaps under 30 minutes ignored; overage above purchased concurrency
Hourly InteractingTime spent on interactionsEnabled per user by the Billing > User > hourlyInteracting permission through the Hourly Interacting User role; administrators and supervisors disqualified (11.5)
Hourly Logged In (legacy)Total time logged inCannot be combined with named or concurrent; covers all user types, including administrators and supervisors
  • New named and concurrent customers get access to Hourly Interacting by default; existing customers gain it at renewal or can order it earlier. Organisations on Hourly Logged In must move to named or concurrent to use Hourly Interacting.
  • Changing a user's licence type is retroactive to the start of the current billing period, so a change late in the month re-measures the whole month.

11.5 The disqualifying permission list

Genesys states that the Hourly Interacting licence may not be held by administrators and supervisors: any user holding any permission on its published list is ineligible, and a user already on Hourly Interacting who is given one is disqualified and loses the licence. The list runs to 323 permissions, shown ten at a time in a searchable table, so review it in a browser.

It is broader than administrator and supervisor suggests. The first page includes analytics:evaluationAggregate:view and analytics:surveyAggregate:view as well as division and grant permissions. An hourly agent given read access to evaluation aggregates, perhaps to see their own scores, becomes a full named or concurrent seat automatically, and because of the retroactive rule, for the whole month.

12

Add-ons, overages and partner seats

Permissions decide more than the base licence. This part covers the add-ons that permissions and ordinary activity trigger, how Genesys bills overage, how to reconcile an invoice, and the partner seats that do not count.

12.1 WEM add-on billing triggers

Genesys documents three ways a user becomes billable for the Workforce Engagement Management add-on. First, every user with administrator permissions for WEM capabilities is billed, and Genesys warns that after an organisation is upgraded, users in the Master Admin, Performance Management Admin, Quality Admin and Quality Evaluator roles may incur WEM charges immediately. Second, agents are billed when certain things happen to them. Third, a user is billed when given the Billing > User > WEMUpgrade permission, which Genesys describes as upgrading the user to a WEM licence.

  • A schedule is created for them in the WFM scheduler.
  • An evaluation is assigned to them, where the base licence does not already include quality management.
  • A voice survey is started for them, or a web survey is sent about them.
  • A coaching session is scheduled for them.
  • A learning module is assigned to them.
  • A gamification point is generated for them.

12.2 What that means operationally

Those are not administrators opting in. They are a planner publishing a rota, an evaluator picking a call, a module being assigned. The first schedule published after the add-on is enabled starts billing for those agents.

Two further rules: an organisation can enable both the WEM and speech and text analytics (STA) add-ons, but each user can hold only one, and WEM takes precedence because it includes more. Transcription use alone does not trigger WEM or STA charges; minutes come from the organisation's shared transcription pool, with overage above it. Since April 2026, administrators control STA and WEM add-on licensing through explicit permissions, and transcription is billed separately per minute. Any cost model written before April 2026 that assumes transcription implies an STA add-on needs rechecking.

12.3 Overage and reconciliation

Genesys separates user-based billing, the named or concurrent users, which has no fair use allowance, from non-user resources such as API calls and data storage, which come with a fair use allowance and are billed only above it. Genesys always bills user overage monthly in arrears, whether the contract is monthly or annual. Its worked example takes the peak users in the usage report, subtracts the contracted users, and bills the difference.

To look at a period, administrators with billing subscription permissions use Account > Subscription for a snapshot of subscription, services and seats, and can run historical usage reports; upgrades appear there once active. To drill into a person, Genesys's route is the Billable Usage report, the licence on the People page (which may have changed during the period), logged-in times in the Agent Status Detail view, or the User Status Detail API, with Concurrent Usage reports for concurrent contracts. Because the People page shows only the current licence, history has to come from the usage report and status views.

12.4 Authorised users do not count

An authorised user is someone with permission to work in an organisation other than their home one. Genesys tracks them separately, and states that they do not affect user counts for licensing and billing. An organisation can have at most 25. They assist with administrative tasks only: alerting, chat, interactions, phone calls and video conferences are not available to them, and their agent dashboard does not load.

Groups make them easier to manage: authorise a group from the home organisation and all members receive the same roles, divisions and permissions, unaffected by others joining or leaving. As our roles and permissions handbook explains, the host organisation is responsible for what they do, and since November 2026 their roles can be scoped to specific divisions.

13

Custom user attributes, and designing the process

Everything above comes together in one joiner, mover and leaver process. One newer element, custom user attributes, adds a step that exists only as an API call.

13.1 Custom user attributes

Genesys describes a custom user attribute as a field defined on user profiles to record a user's entitlements; its example is a LegalEntity attribute listing the legal entities a user may work with. You create the schema through an API, assign values to users through another, then use the attributes in attribute-based access policies, which compare the user's values with a conversation's customer access attributes to allow or deny access.

  • Since February 2026 the feature is API-only, not yet in the Genesys Cloud interface, so there is no admin screen to check a value.
  • It needs the custom attributes schema permissions (add, edit, delete, view) plus Directory > User > Edit, and administrators can manage only users within their authorised scope.
  • Genesys documents no SCIM mapping for custom user attributes, so values must be fed by the assignment API: integration work with an owner.
  • Errors appear when a policy is saved: referencing an undefined or misspelt attribute returns an error.
  • Nothing manages their lifecycle. An attribute nobody owns becomes a policy that silently denies access, or wrongly allows it.

13.2 Three decisions before anything else

Decide the system of record for identity: the SCIM provider, or a named owner of a CSV process (parts 2 and 3). Decide the division naming standard and write it down before mappings are built (part 4). And decide the licence policy: which roles map to which licence, and who must approve a role change that alters one (part 11).

13.3 Joiners

A joiner process (QVCCS practice)
StepActionWhy
1Create the identity in the source directory and assign it to the Genesys Cloud applicationWith one-way sync, this is the only durable place to do it
2SCIM creates the user, with division mapped to an existing division or left blank for HomeThe mapping does not create divisions (part 4)
3Directory group membership adds the user to the Genesys Cloud group that carries the roleThis survives deletion and re-enabling (part 5)
4Check the licence tier once in the first weekIt is derived automatically and invisible unless looked for (part 11)
5Send the invitation; the user logs in and sets up MFA if nativeBilling starts at first login, not at creation (parts 1 and 6)

13.4 Movers

Change group membership and the division attribute upstream, and never edit what is synced. Check whether the mover's new permissions cross into the hourly disqualifying list or a higher licence tier, because a department move can be a commercial event. Remember that a CSV import will not remove an old role, so a role on the old group must be taken off deliberately.

13.5 Leavers

  1. Remove upstream: out of the app's scope in Entra ID, or unassigned in Okta. The user becomes inactive in Genesys Cloud.
  2. Verify in Genesys Cloud: filter the People page by status and confirm the user cannot authenticate.
  3. Set the retention period as a number of days: inactive for that period, then delete. Without a number, deletion never happens.
  4. Delete knowing what remains: permissions go, but email, performance data, conversation and chat history, documents and voicemails remain, and the user moves to Home.
  5. Do not reuse the email address or account.
  6. Handle erasure separately, per person, through the GDPR API, never as a bulk job.

13.6 The exception path

Break-glass accounts, accounts with no directory record and any native-login survivors each need a named owner, an expiry date and a review, because they are exactly the population that falls between the SCIM process and the audit.

14

Review routines and what goes wrong

Four routines keep the lifecycle honest, each using capabilities Genesys documents, followed by the failures we see most and their fixes.

14.1 Review routines

Lifecycle review routines (QVCCS practice)
CadenceReviewUsesCatches
WeeklyProvisioning failures and unexpected changesIdentity provider provisioning and audit logs; Genesys Cloud Audit Viewer (14-day window)Changes on the identity provider's side, mapping errors, stalled syncs
MonthlyBillable against contractedAccount > Subscription; Billable or Concurrent Usage reports; Agent Status DetailOverage, and which population caused it
MonthlyLicence tier driftRole catalogue compared with each role's License column; licence type on the People pageSilent tier changes and hourly disqualifications
QuarterlyAccess review and clean-upPeople page filters by role, division, reports-to and status; the Unused columnDormant accounts, role sprawl, accounts with all-division scope
  • We add an SSO certificate register with expiry dates, 90-day reminders and a signed-request test for each provider.
  • We also run an identity reconciliation report comparing the identity provider's assignment list with Genesys Cloud's active users. The difference is the clearest measure of how well the process works, and the only reliable way to catch users active in the directory but inactive in Genesys Cloud, or deleted in Genesys Cloud but still assigned in the directory.

14.2 Twelve things that go wrong

Common user lifecycle problems, causes and fixes
SymptomLikely causeFix
A user cannot log in with SSO at allThe assertion's email does not match the Genesys Cloud recordAlign the mapped identity, or configure a non-email identifier (part 8)
No identity provider icon on the login pageThe SSO configuration is incompleteCheck the provider entry; Genesys says this is a configuration fault (part 8)
SSO fails for everyone after a certificate changeThe new certificate was not given to the identity provider in timeUpload during the multi-certificate window and keep an expiry register (part 9)
A chat notification webhook fails after SSO enforcementSSO-only breaks password-based webhook authenticationInventory password-based integrations first; move them to OAuth clients (part 9)
New users land in Home and cannot see their queuesThe division value does not match an existing divisionBuild divisions first and treat names as a contract (part 4)
The provisioning log shows endless updates for the same usersPhone number format differs from E.164Use StripSpaces or convert numbers at the source (part 4)
Clearing a directory attribute leaves the old value in Genesys CloudMicrosoft's sync ignores empty valuesPush a deliberate non-empty value, or change the mapping (part 4)
A rehired seasonal agent is active but sees nothingDeleting then re-enabling does not restore roles, not even EmployeePut roles on groups and let the directory manage membership (part 5)
Job titles vanished after an importBlank extension, title or department columns override existing valuesNever leave those columns blank; generate the file (part 2)
Agents lost routing skills after an importThe skills column replaces rather than addsExport current skills first, or edit profiles (part 2)
Duplicate roles appearSpelling errors or trailing spaces in the CSVProofread, use the template and reconcile role names (part 2)
An occasional agent became a full seatThey were given a permission on the hourly disqualifying listGuard hourly populations and recheck the list after releases (part 11)

Questions

Common questions

Does Genesys Cloud SCIM sync changes back to Entra ID or Okta?

No. Genesys states that SCIM currently syncs one way only, from the identity management system to Genesys Cloud, and that changes made in Genesys Cloud are not synced back and may be overwritten. Treat the directory as the system of record, fix data there, and agree how Genesys Cloud administrators report data problems to the directory team.

What happens when a user is removed from Entra ID?

Removing a user from the app's scope, or soft-deleting them, makes them inactive in Genesys Cloud. When Entra ID hard-deletes the user, by your action or its maintenance schedule (currently 30 days after removal or soft deletion), Genesys Cloud deletes them. Inactive users cannot log in and keep their roles; deleted users lose their permissions.

Why does a re-enabled user have no roles in Genesys Cloud?

If a user is deleted in Genesys Cloud and later re-enabled through Okta, Genesys Cloud makes them active again but does not restore the Employee role or any manually added roles. Genesys recommends assigning roles to a group in Genesys Cloud and adding the user to that group from the directory, so roles return automatically.

Does deleting a Genesys Cloud user delete their data?

No. Deletion stops the user logging in and removes their permissions, but Genesys keeps related information such as their email address, performance data, conversation and chat history, documents and voicemails. That data can be removed through the GDPR API, one person and identifier at a time; Genesys warns that bulk requests may be cancelled.

Do SSO users get Genesys Cloud MFA prompts?

No. Genesys states that it supports MFA for native login only and that SSO users do not receive MFA prompts. For SSO users, the second factor is enforced by the identity provider, so that is where security controls and audit evidence belong. Genesys Cloud MFA remains important for break-glass and other native-login accounts.

Can an hourly interacting user lose that licence?

Yes. Genesys publishes a list of 323 permissions that disqualify a user from Hourly Interacting. A user given any of them, including evaluation or survey aggregate view permissions, loses the hourly licence and is metered under the named or concurrent model, and licence type changes apply retroactively from the start of the billing period.

Sources

  1. Deprecation: Genesys Cloud SSO certificate expiry – Genesys Cloud Resource Centerhelp.genesys.cloud
  2. New Multi-Factor Authentication (MFA) device options – Genesys Cloud Resource Centerhelp.genesys.cloud
  3. About Genesys Cloud SCIM (Identity Management) – Genesys Cloud Resource Centerhelp.genesys.cloud
  4. Roles and permissions overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  5. About single sign-on (SSO) – Genesys Cloud Resource Centerhelp.genesys.cloud
  6. Add multiple single sign-on providers to Genesys Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  7. Bulk upload of people data – Genesys Cloud Resource Centerhelp.genesys.cloud
  8. Add people to your organization – Genesys Cloud Resource Centerhelp.genesys.cloud
  9. Add roles – Genesys Cloud Resource Centerhelp.genesys.cloud
  10. Add Workforce Engagement Management to your subscription – Genesys Cloud Resource Centerhelp.genesys.cloud
  11. Assign roles, divisions, licenses, and add-ons – Genesys Cloud Resource Centerhelp.genesys.cloud
  12. Authorized users and groups – Genesys Cloud Resource Centerhelp.genesys.cloud
  13. Change your password – Genesys Cloud Resource Centerhelp.genesys.cloud
  14. Concurrent licensing model billing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  15. Configure Microsoft Entra ID for Genesys Cloud SCIM (Identity Management) – Genesys Cloud Resource Centerhelp.genesys.cloud
  16. Configure Okta for Genesys Cloud SCIM (Identity Management) – Genesys Cloud Resource Centerhelp.genesys.cloud
  17. Configure the Genesys Cloud browser extensions – Genesys Cloud Resource Centerhelp.genesys.cloud
  18. Configure the UC tools integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  19. Customer access attributes and custom user attributes overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  20. Delete someone from your organization – Genesys Cloud Resource Centerhelp.genesys.cloud
  21. Edit user configuration data – Genesys Cloud Resource Centerhelp.genesys.cloud
  22. Enable multi-factor authentication – Genesys Cloud Resource Centerhelp.genesys.cloud
  23. Genesys Cloud and GDPR compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
  24. Genesys Cloud licenses and billing – Genesys Cloud Resource Centerhelp.genesys.cloud
  25. Hourly interacting license disqualifying permissions – Genesys Cloud Resource Centerhelp.genesys.cloud
  26. Hourly licensing model billing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  27. Invite people to your organization – Genesys Cloud Resource Centerhelp.genesys.cloud
  28. Log in for the first time – Genesys Cloud Resource Centerhelp.genesys.cloud
  29. Log in to Genesys Cloud using single sign-on (SSO) – Genesys Cloud Resource Centerhelp.genesys.cloud
  30. Manage licenses – Genesys Cloud Resource Centerhelp.genesys.cloud
  31. Manage multi-factor authentication (MFA) devices – Genesys Cloud Resource Centerhelp.genesys.cloud
  32. Overview of the People page – Genesys Cloud Resource Centerhelp.genesys.cloud
  33. Named licensing model billing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  34. Overview of multi-factor authentication (MFA) – Genesys Cloud Resource Centerhelp.genesys.cloud
  35. Products, roles, and permissions list – Genesys Cloud Resource Centerhelp.genesys.cloud
  36. Reset your password – Genesys Cloud Resource Centerhelp.genesys.cloud
  37. SCIM and Genesys Cloud field mappings – Genesys Cloud Resource Centerhelp.genesys.cloud
  38. Single sign-on overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  39. Set user status – Genesys Cloud Resource Centerhelp.genesys.cloud
  40. Configure Genesys Cloud to authenticate with SSO only – Genesys Cloud Resource Centerhelp.genesys.cloud
  41. User overages on your invoice – Genesys Cloud Resource Centerhelp.genesys.cloud
  42. View your billing and usage summary – Genesys Cloud Resource Centerhelp.genesys.cloud
  43. What users can expect after SSO setup – Genesys Cloud Resource Centerhelp.genesys.cloud
  44. Work with the People page – Genesys Cloud Resource Centerhelp.genesys.cloud
  45. Can we change from a Concurrent or a Named license type to an Hourly Interacting license type? – Genesys Cloud Resource Centerhelp.genesys.cloud
  46. Can we change from an Hourly Interacting license type to a Concurrent or a Named license type? – Genesys Cloud Resource Centerhelp.genesys.cloud
  47. How can we see our usage statistics for the current billing period? – Genesys Cloud Resource Centerhelp.genesys.cloud
  48. ISV applications FAQs – Genesys Cloud Resource Centerhelp.genesys.cloud
  49. 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
  50. What causes Genesys Cloud to change the status of a Microsoft Entra ID user to inactive or to delete a user? – Genesys Cloud Resource Centerhelp.genesys.cloud
  51. What happens if I unassign a user from the Genesys Cloud application in Okta? – Genesys Cloud Resource Centerhelp.genesys.cloud
  52. What happens when I delete a user in Genesys Cloud and later reenable the user in Okta? – Genesys Cloud Resource Centerhelp.genesys.cloud
  53. What happens when I delete a user's account? – Genesys Cloud Resource Centerhelp.genesys.cloud
  54. Why are Genesys Cloud user records unexpectedly changed after an update to Microsoft Entra ID? – Genesys Cloud Resource Centerhelp.genesys.cloud
  55. Genesys Cloud licenses and billing – Genesys Cloud Resource Centerhelp.genesys.cloud
  56. April 20, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  57. December 21, 2022 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  58. December 6, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  59. February 6, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  60. February 9, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  61. January 26, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  62. July 22, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  63. July 31, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  64. May 29, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  65. October 18, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  66. Troubleshoot Genesys Cloud SCIM (Identity Management) – Genesys Cloud Resource Centerhelp.genesys.cloud
  67. Configure SSO identity provider without email address – Genesys Cloud Resource Centerhelp.genesys.cloud
  68. Configure OneLogin for Genesys Cloud SCIM (Identity Management) – Genesys Cloud Resource Centerhelp.genesys.cloud

Last reviewed

We work by introduction

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

Who to contact