Skip to content

Setup Guide

Before we begin, you will need to collect the following information. Once you have all the items, please send them to devops@solve4me.com.br:

Required Information

  • Authorization URL
  • Code Authorization PKCE OAuth Client ID
    (Do not send the secret)
  • Organization Name
  • Organization ID

Server Credentials

  • Server OAuth Client ID
  • Server OAuth Client Secret
    (Note: We need the secret for the server client, not the login OAuth client)

Follow these steps to generate the required information and configure your environment.

  1. Gather your organization’s Short Name and Organization ID under Organization Settings.

    Genesys Cloud Organization Settings showing Company Name, Short Name and Organization ID

    Create an OAuth Client with the following configuration:

    Grant Type:

    Code Authorization / PKCE

    Authorized redirect URIs:

    s4megenesysmobile4me://callback
    https://apps.<your Genesys Cloud region>

    Scope:

    The scope will vary depending on whether your organization has enabled Enforce Scopes.

    Enforce scopes enabled
    analytics:readonly, assistants:readonly, authorization:readonly, conversations, external-contacts:readonly, integrations, messaging:readonly, notifications, organization:readonly, presence, recordings:readonly, response-management:readonly, routing:readonly, scripts:readonly, speech-and-text-analytics:readonly, stations:readonly, user-basic-info, users, voicemail:readonly
    Enforce scopes disabled
    analytics, conversations, geolocation, notifications, organization:readonly, presence, routing:readonly, stations, users:readonly

    Preview:

    Genesys Cloud login OAuth client configured with the Code Authorization / PKCE grant type, redirect URI and scopes

  2. First, you need to create a Role with specific permissions for the server:

    • Analytics > Agent Conversation Detail > View
    • Analytics > User Observation > View
    • Presence > User Presence > Edit

    Genesys Cloud role permissions for the Mobile4me backend server

  3. Create a new OAuth Client using the role you just created:

    Setting Value
    Grant Type Client Credentials
    Role The role created in Step 2

    Genesys Cloud Add New Client form with the Client Credentials grant type selected

    Assign the role to the OAuth client for the appropriate division on the Roles tab.

    Assigning the role and division to the Mobile4me backend OAuth client

  4. Send the Client ID and Client Secret of this Server OAuth client to us via email at: devops@solve4me.com.br


List of roles that we recommend assigning to the user within the same division.

This is a recommendation to ensure full functionality of Mobile4ME. However, each agent may have specific feature restrictions, which should be evaluated according to the organization’s requirements.

Recommended user roles
  • analytics:conversationDetail:view
  • analytics:agentConversationDetail:view
  • assistants:copilot:view
  • assistants:queue:view
  • assistants:queueUserAssignment:view
  • conversation:call:accept
  • conversation:call:add
  • conversation:call:record
  • conversation:callback:accept
  • conversation:callback:create
  • conversation:communication:blindTransfer
  • conversation:communication:consultTransfer
  • conversation:communication:disconnect
  • conversation:communication:view
  • conversation:conference:add
  • conversation:email:accept
  • conversation:email:create
  • conversation:email:send
  • conversation:message:accept
  • conversation:message:create
  • conversation:message:view
  • conversation:participant:wrapup
  • conversation:recording:pause
  • conversation:recording:snippetRecord
  • conversation:suggestion:edit
  • conversation:suggestion:view
  • conversation:webmessaging:accept
  • conversation:webmessaging:create
  • conversation:webmessaging:view
  • directory:user:view
  • externalContacts:contact:view
  • integrations:action:execute
  • messaging:integration:view
  • outbound:contact:add
  • outbound:contact:edit
  • outbound:dnc:add
  • presence:presenceDefinition:view
  • recording:recording:view
  • recording:recordingSegment:view
  • responses:library:view
  • responses:response:view
  • routing:agent:onqueue
  • routing:queue:search
  • routing:queue:view
  • routing:wrapupCode:view
  • scripter:publishedScript:view
  • telephony:otherStationAssociation:edit
  • telephony:selfStationAssociation:edit
  • telephony:selfStationAssociation:view
  • voicemail:acdVoicemail:download
  • voicemail:acdVoicemail:stream
  • workitems:workitem:add

Last updated: