Cirrus Insight supports a variety of deployment models to fit different email and Salesforce environments. This article provides guidance on how Cirrus Insight functions in multi-tenant environments and outlines available deployment options.
A multi-tenant environment refers to an IT setup where users or departments operate on separate, independently managed email or server instances—often across different domains or organizations—while still needing to use shared tools like Salesforce or Cirrus Insight. This structure can make centralized deployment and authentication more complex, requiring specific considerations for configuration and access.
Example 1: A national organization has multiple regional offices, each with its own Office 365 tenant and local IT admin. Each location needs Cirrus Insight configured to sync with its email environment, while still aligning with organization-wide processes.
Example 2: Some locations sync to their own Salesforce environments, while others share a centralized Salesforce instance. Cirrus Insight supports both models—enabling tailored sync per tenant while allowing oversight and integration at the organizational level.
Cirrus Insight’s Sidebar can be deployed based on the email platform your organization uses:
For Office 365, Exchange Online, or Exchange On-Prem (2013 or newer):
The Sidebar is deployed as an Office Web Add-In, accessible in both the Outlook web and desktop versions.
For Gmail / Google Workspace environments:
The Sidebar is deployed as a Chrome Extension, available via the Chrome Web Store.
Beyond the Sidebar, Cirrus Insight offers powerful productivity tools including:
These services require users to connect both their Salesforce and email accounts. Two connection methods are available:
1. User-Managed OAuth Connections
Each user independently authenticates and connects their Salesforce and email accounts using OAuth.
2. Admin-Managed Service Accounts
Administrators can configure centralized connections via Salesforce Service Accounts and Email Service Accounts.
In a multi-tenant email environment—where users are distributed across multiple, independent mail server instances—centralized deployment can be more complex.
Typical Setup:
Users manage their own OAuth connections to Salesforce and their email accounts.
This approach is necessary because administrators often lack access to a unified mail platform that spans all tenants.
Alternative Setup for Collaborative Environments:
Separate Child Organizations within Cirrus Insight:
Admins can create and manage distinct child orgs for each tenant.
A child org lets an admin group users under their own set of parameters, configurations, and connections.
A few rules govern how users relate to orgs:
A user belongs to exactly one org at a time.
Every user needs a unique email address across the parent org and all of its child orgs.
Users are created or imported into whichever child org is active at the time. Switch to the target child org first, then create or import.
Moving an existing user between orgs: Creating new users and importing them is self-service. Moving a user who already exists from one org to another is not—open a support ticket and we’ll transfer them for you.
Importing from Salesforce into an empty child org: The Salesforce import needs at least one user already in the child org before it will run. Add one user manually first, then import the rest.
Sync logs are scoped to whichever org is active, so switch to the child org you want to review before you start.
Switch to the child org.
Open the sync logs in the admin dashboard.
Filter to the user and date range you’re investigating.
Export the results. The export downloads as a CSV file.
Bulk export across users isn’t available: Sync logs export one user at a time. To collect logs for several users, review each user individually and export separately.