Email Integration Full Deployment Scenarios¶
Setting up RGES Add-In and Synchronization for multiple end users is a standard procedure performed by the local mail server Admin and Salesforce/RGES admin.
The following scenarios can be applied to deploy Email Sidebar
Note
Email Sidebar is not a standalone application: it is installed in MS Outlook Desktop, Web, or Mobile implementation as an Add-In, or in the Chrome browser as a browser Extension for Gmail
Tip
For big Enterprise customers Email Sidebar can also be installed in a private corporate Azure cloud on back end, if that is required by the company’s security requirements. Contact our CSM team for more information about this possibility. The deployment procedures used in such scenario are identical to the regular ones used for RevenueGrid Azure servers deployment
Scenarios for MS Exchange or Office 365 mail accounts via RGES Outlook Add-In¶
Tip
Also see this article to learn about all mail server connectivity types compatible with Email Sidebar
| Deployment scenario | Required Admin actions* | Required User actions (Registration wizard recommended) |
|---|---|---|
| A. Full RGES deployment for all users by the Admin, except for individual Add-In logon: see the scenario F below (involves Impersonated Access, thus not suitable for all configurations) | 1. Set up an Impersonating service account in MS Exchange 2. Mass-deploy the Add-In for all end users in MS Exchange or Office 365 via Impersonating account. RGES Sync will be auto-activated on the users’ first logon to the Add-In |
Log on to the Add-In in MS Outlook/Office.com |
| B. Only Add-In mass deployment by the Admin | 1. Mass-deploy the Add-In for all end users in MS Exchange or Office 365 (without Impersonating account). In this case RGES Sync is to be activated by the end users | 1. Log on to the Add-In 2. Activate RGES Sync |
| C. Only RGES Sync activation, through Impersonated account | 1. Set up an Impersonated service account in MS Exchange / Office 365 2. Set up mailbox access in RGES admin panel |
1. Install the Add-In 2. Log on the the Add-In |
| D. Full installation by individual end users | No special Admin actions save for * | 1. Install the Add-In 2. Log on to the Add-In 3. Activate RGES Sync |
| F. Automatic RGES Sidebar logon using a Salesforce service account | Create a dedicated Salesforce account with special permissions and configure it to impersonate RGES users’ accounts. See this article for details. | 1. Install the Add-In 2. Activate RGES Sync via the Sidebar |
* there are two additional local Admin actions to be performed for every listed scenario:
❍ ensure that the Add-In’s connections are not blocked by the corporate firewall and
❍ install the Revenue Grid managed package in Salesforce to ensure maximum interaction efficiency
Scenarios for Gmail account via RGES Chrome Extension¶
[this section is work-in-progress]
| Deployment scenario | Required Admin actions* | Required User actions (Registration wizard recommended) |
|---|---|---|
| A. Full RGES deployment for all users by the Admin, except for individual Extension logon (involves Impersonated Access) Can only be performed for Windows OS, using MS Active directory |
1. Mass-install the Chrome Extension for all end users 2. Configure a service Gmail account and mass-sign in to Salesforce for all end users through it |
Login to the corporate Gmail / Google Workspace (G Suite) account in Chrome Browser |
| B. The Chrome Extension is deployed for all users by the Admin. Using Google native procedures or MS Active Directory |
Using Google native procedures Using MS Active Directory means |
1. Login to the corporate Gmail / Google Workspace (G Suite) account in Chrome Browser 2. Sign in to the Chrome Extension |
| C. Chrome Extension’s Synchronization is mass-activated by the Admin | Configure a service Gmail account and mass-sign in to Salesforce for all end users through it |
1. Install the Chrome Extension 2. Login to the corporate Gmail / Google Workspace (G Suite) account in Chrome Browser |
* there are two additional local Admin actions to be performed for every listed scenario:
❍ Ensure that the Extension’s connections are not blocked by the corporate firewall and
❍ Install the Revenue Grid managed package in Salesforce to ensure maximum interaction efficiency
We would love to hear from you