Skip to main content
This page lists every Genesys Cloud permission the role OpenCX uses can hold. Read it before you connect, when a feature stays off, or when Health asks you to add a permission. Signing in creates the role for you and grants it in the divisions you choose. If you create it yourself, grant it in the divisions OpenCX should work in.
The role reads and writes only in the divisions it’s granted in, so OpenCX can’t see agents, queues or flows outside them. Its message flow goes in a chosen division: Home if you chose it, otherwise the first by name. Genesys doesn’t divide messaging connections, the Assist panel or presence definitions, so those are org-wide, and contacts with no division stay visible.It can’t change queues. Without routing:queue:add it can’t create them either. Creating an email route or adding queue members always needs a Genesys login with routing write access.

Required

Optional, added when the admin holds them

These depend on your Genesys licence and never block connecting. Signing in adds the ones the admin holds. Without them, connecting works and only that feature stays off. Calls and callbacks in Show every Genesys conversation, and notes on external contacts in both directions, need nothing beyond the permissions above.

Optional, added by you

Add these to the role yourself if you want them. Signing in doesn’t add them.

For the admin who signs in

To sign in, the admin also needs authorization:role:view, authorization:role:add, authorization:role:edit, authorization:division:view, authorization:grant:add and oauth:client:add. Changing divisions on a later sign-in also needs oauth:client:edit. If your org enforces OAuth scopes, the first sign-in also needs oauth:client:authorize, to approve OpenCX under Authorized Applications.

Connect Genesys Cloud

Sign in or use a client ID and secret.

Fix connecting and setup

Missing permissions, divisions and sign-in errors.