What is the Multi-Org Feature?
The Multi-Org feature allows Spekit users to view Spekit icons in more than one Salesforce organization. This feature is only available for Enterprise customers.
Why should you enable the Multi-Org Feature?
If your Spekit users are active in more than one Salesforce organization in your company, the Multi-Org feature can be enabled and configured to allow end-users to view Spekit icons in each Salesforce organization they use.
Example: https://d6g000006uliseam-dev-ed.lightning.force.com/ is the primary Salesforce URL that Spekit is connected to.
If Multi-Org is enabled for the Spekit instance, the Spekit Account Admin role users can make edits to Topics in Spekit and add another Salesforce URL such as this example:
https://lightningspekit-dev-ed.lightning.force.com/
How do I enable the Multi-Org Feature for my company?
To enable the Multi-Org feature, please send a request to support@spekit.co, and our team will handle the process on our end. Once enabled by the Spekit team, your internal Spekit Account Admin will need to configure the topic(s) Salesforce URLs.
What is the Multi-Org Feature Terminology?
- URL: The address of a web page.
- Domain: In the context of networking, it refers to any group of users, workstations, devices, printers, computers, and database servers that share different types of data via network resources.
- Subdomain: A domain that is part of a larger domain.
- Salesforce Org: Short for Salesforce Organization or the site URL where the company uses Salesforce.
How does the Multi-Org Feature impact Spekit icons?
- Objects, fields, and picklist icons will be shown by default only on synced org.
- To show objects, fields, and picklist icons on non-synced org, we need to link the domain URL to a Topic and add relevant Speks.
- Custom Speks icons will not show until you add the domain URL to the Topic.
How does the Multi-Org Feature impact the Spekit sidebar?
1.) Related Speks will be shown in the Spekit Chrome Extension sidebar when you are on a Salesforce object page (e.g. Account, Opportunity) for a synced Salesforce org.
2.) Related topics will be shown in the Spekit Chrome Extension sidebar when you are on the Salesforce object page (e.g. Account, Opportunity) for a non-synced Salesforce org.
3.) Related topics will be shown in the Spekit Chrome Extension sidebar when you are on non-object pages inside a Salesforce org.
4.) Related topics will be shown in the Spekit Chrome Extension sidebar when you are on non-Salesforce domains.
How to edit a Topic to work with 2 different Salesforce Organizations
From the Spekit Web App - in a Topic edit view:
1.) Enter the URL in the Domain URL contains field i.e., https://lightningspekit-dev-ed.lightning.force.com/lightning/o/Opportunity/list?filterName=Recent
2.) Apply check on Include path and domain.
- The path is parsed to the Path text field, i.e.,/lightning/o/Opportunity/list
- Add a path button will also appear, and a user can add multiple paths with the preceding forward slash.
- Unchecking the Include path and domain will remove the path field(s), and the values inside the path field(s) will be lost.
3.) If an Org user wants to show Speks for non-sync orgs wherever a URL that contains Opportunity keyword i.e., https://lightningspekit-dev-ed.lightning.force.com
- Org user will simply enter the domain/subdomain in the Domain URL contains field and add /Opportunity keyword.
The contain logic will let the non-sync org users view the Speks wherever an opportunity keyword exists in the URL path i.e.
https://lightningspekit-dev-ed.lightning.force.com/lightning/o/Opportunity/list
https://d6g000006uliseam-dev-ed.lightning.force.com/lightning/o/Opportunity/list
Validation Rules on Path field
1.) Empty string/blank field is not allowed.
2.) Only Preceding Forward Slash “/” is not allowed.
3.) String without Preceding Forward Slash “/” is not allowed.