Salesforce Multi-Connect

How do I connect one Salesforce instance to multiple instances of Ambition?

What do I need to know about administering multiple instances of Ambition?

Can Salesforce users be synced to multiple Ambition instances?

How does multi-connect support impact Salesforce resources?

How do I connect one instance of Salesforce to multiple instances of Ambition?

Within the first Ambition instance, Ambition's Salesforce managed package will be authorized and installed. Learn more about installing here.

In subsequent Ambition instances, only the authorization step will need to occur as Ambition's managed package is already installed in Salesforce.

Can I connect one instance of Salesforce to multiple instances of Ambition without installing the Managed Package in Salesforce?

Yes. Ambition offers an API-only connection with Salesforce which can support connecting one instance of Salesforce to multiple instances of Ambition. Learn more about the API-Only option here.

What do I need to know about administering multiple instances of Ambition?

Is any data transferred between Ambition instances?

No, data from multiple Ambition instances will not be aggregated in any way, and data will not be transferred between instances. Metrics, users, groups, and any features will be specific to each instance and will need to be recreated within each instance of Ambition as needed.

Ex. If a "Closed Won $" metric should be used in each instance of Ambition, the metric will be created and managed as needed within the Salesforce metric library of each Ambition instance.

While data is not transferred between Ambition instances, each instance of Ambition will receive Salesforce data for all Salesforce users. The exact data Ambition receives from Salesforce will be dependent on the specific metrics present in each Ambition instance, and Ambition will only create records and metric values for active users in each respective Ambition instance.

Can Salesforce users be synced to multiple Ambition instances?

Yes, Salesforce users can be synced to multiple Ambition instances.

Important to note: If a user is synced to multiple Ambition instances, the Ambition tab and widgets they see in Salesforce will remain set to the first Ambition instance where they were synced.

Ex. If user A is first synced to Ambition instance 1 and then synced to Ambition instance 2, user A's Ambition tab and widgets will remain set to displaying content from Ambition instance 1.

Each instance of Ambition will receive Salesforce data for all Salesforce users, but Ambition will only create records and metric values for active users in each respective Ambition instance.

Can I use Salesforce single sign-on with multiple Ambition instances?

Yes. In the context of having multiple Ambition instances that will be connected to the same Salesforce, you will want to create a separate connected app and separate permission set for each Ambition instance that will utilize Salesforce single sign-on.

Can multiple instances of Ambition send Workflows to one instance of Slack or MS Teams?

No, due to the nature of our bot-based integrations with Slack and MS Teams, sending workflows from multiple Ambition instances to one instance of Slack or MS Teams is not supported.

Can multiple instances of Ambition send Workflows to one instance of Webex?

Yes. Sending workflows from multiple instances of Ambition to one instance of Webex is supported due to the user level authorization of Ambition's Webex app.

How does multi-connect support impact Salesforce resources?

Each connected instance of Ambition will create 2 Apex Jobs in Salesforce: PusherScheduler and AsyncReportScheduler.

Each connected instance of Ambition will use API calls as outlined here.