Difference between revisions of "PEC-CAB/Current/CABPEGuide/Provision"
From Genesys Documentation
m (Text replacement - "Genesys Engage" to "Genesys Multicloud CX") |
m (Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement") |
||
| Line 1: | Line 1: | ||
{{Article | {{Article | ||
|Standalone=No | |Standalone=No | ||
| − | |DisplayName=Provision Genesys | + | |DisplayName=Provision Genesys Engagement Service |
| − | |Context=Learn how to provision Genesys | + | |Context=Learn how to provision Genesys Engagement Service. |
|ComingSoon=No | |ComingSoon=No | ||
|Role=Administrator | |Role=Administrator | ||
Revision as of 21:15, November 9, 2021
This topic is part of the manual Genesys Callback Private Edition Guide for version Current of Callback.
Contents
Learn how to provision Genesys Engagement Service.
Related documentation:
RSS:
Provision GES
For basic provisioning of GES to support the use of callback, see Provisioning Callback in Designer.
Guidance on how to configure Click-to-Call-In, CAPTCHA, Push Notifications, and other more advanced use cases can be found in the Callback Administrator's Guide.
You must assign users to specific Roles and Access Groups for access to the Callback UI. Genesys Callback uses Role-based-access-control (RBAC) to allow and restrict users' activities within the Callback UI. For more information about Callback-related Roles and Access Groups, see Controlling user access.
Comments or questions about this documentation? Contact us for support!