A single Salesforce org can connect to more than one Egnyte domain with the latest Salesforce version. Each Salesforce record syncs to exactly one domain, chosen automatically from the record’s data. This guide explains how to connect additional domains, configure record routing, manage per-domain settings, and remove domains.
Multidomain is useful when different business units, subsidiaries, or regions use separate Egnyte domains but share one Salesforce org. For example, after a merger or acquisition, or where content must stay separated by entity.
Some of the key terms and concepts associated with the Salesforce integration include:
- Default Domain: The org’s original (first) Egnyte domain. Records that do not match any routing rule sync here.
- Discriminator Field: A field on the record whose value determines which domain the record syncs to.
- Division Routing: An alternative to the discriminator field for orgs using Salesforce Divisions: records route by division name.
- Setting Name: The identifier given to a connected domain when configuration is created. The configuration cannot be renamed afterwards, so choose it deliberately.
- One Record, One Domain: Every record maps to exactly one domain. A record cannot sync to two domains at once.
Prerequisites
Egnyte for Salesforce version 3.11 or later installed in the org.
Egnyte Administrator Permission Set OR Full Salesforce Org Administrative Rights as of 3.11, as one of these is required to edit Egnyte settings.
Egnyte admin credentials for each domain that needs to be connected.
Salesforce Integration licenses must be provisioned for each individual Egnyte domain.
Connecting an Additional Domain
Login to Salesforce as Administrator.
Open the Egnyte Settings page in the Salesforce org.
-
Click on Add Another Domain and enter the domain details, including a Setting Name.
-Setting Name cannot be renamed.
-The setting name is case insensitive and must be unique. Click on Save after entering the details
-
Authenticate with an Egnyte admin account for additional domain to complete the OAuth connection. Finally click Continue
- Multidomain mode is enabled automatically when the first additional domain is connected.
- Invalid multidomain configurations are rejected at save time with a clear message. If a save is rejected, correct the associated issue and save again.
Configuring Record Routing
Egnyte Sync Configuration is used to determine the routing of records to each individual domain. For each object per domain, a separate Sync Configuration record is maintained that defines the settings specific to each domain. This routing determines which domain each record syncs to. There are two options
Option A: Discriminator Field
Create a Custom Text Field on the object (For example - EgnyteDomain__c) to hold the Setting Name per record or use an existing field, this is the Discriminator Field. For more information on creating a custom text field, refer here
Go to New Egnyte Sync Configuration.
-
Fill in the Object + Folder Details. Since multidomain is on, two extra columns would appear:
Setting Name (Multidomain): pick the domain (default, acme, …).
Setting Name Field (Multidomain): pick the discriminator field chosen (same field for every domain of this object).
-
Enter all the details and Save.
Setting Name and Name Field can be adjusted on Egnyte Sync Configuration Edit screen.
Option B: Routing by Division
Orgs using Salesforce Divisions can route by division name instead of a custom field. Each additional domain setting has to be named exactly the same as the corresponding Divisions (For example- for Division EMEA please name the setting for mapped domain EMEA and select Division matched by division name) as Setting Name Field on the Sync Config.
Fallback Behavior
Any record whose discriminator or division value does not match a configured domain safely falls back to the default domain. Unmatched records never produce an error.
Per-Domain Sync Configurations
In multidomain mode, sync configurations are defined per object per domain. Each configuration has its own folder templates and metadata structures, fully independent of other domains. Create and edit sync configurations from the Egnyte Sync Configurations as described earlier by selecting the domain configuration is applicable to.
Per-Domain Settings
The following are held separately for each connected domain:
Credentials / OAuth connection
Default permission and community permission settings
Metadata namespace and scope
Display options
Working Across Domains
My Egnyte Tab
A domain picker on the My Egnyte tab lets users browse the file system of any connected domain. On record pages no picker is shown and the domain always comes from the record itself.
Egnyte Users Tab
Each domain has its own user base and seat counts. A domain picker on the Egnyte Users tab controls which domain the user list, seat totals, and Remove mapping action apply to.
Canvas App and Embedded View
The Egnyte Canvas app and embedded view are domain-aware: opening files or folders from a record always targets that record’s domain.
Bulk Synchronize
The bulk Synchronize backfill follows each record’s own domain, as do folders, files, notes, attachments, enhanced notes, metadata, and mapping deletion.
A sync run processes one domain at a time. Records for other domains in the same batch are picked up on the next run. When mixed domain batches are processed users can expect a small delay, not an error.
Deleting a Connected Domain
- Open the Egnyte Domain Configuration page and select the domain to remove.
- Click Edit, then click Delete Domain. A confirmation screen lists exactly what will be deleted - the domain and all of its configuration including related templates and metadata configurations.
-
Check the confirmation checkbox and click the Delete Domain button when ready. If this was the last additional domain, the org reverts to single-domain operation.
Deleting a domain does not automatically remove generated Apex triggers for custom objects that no other domain uses. The confirmation screen flags these so the users can remove them manually.
Known Limitations
One record maps to one domain; a single record cannot sync to more than one domain at a time.
Sync runs process one domain at a time; records for other domains are picked up on the next run.
A domain’s Setting Name cannot be renamed once created.
Flow action invocables (folder creation/move/delete, permissions, file upload, link creation, metadata) act on the default domain only.
Deleting a domain does not auto-remove generated Apex triggers for custom objects no other domain uses.
Frequently Asked Questions
Do the Users Need to Do Anything After Upgrading to Version 3.11 if They Use One Domain?
No. Single-domain orgs behave exactly as before and it is not required to migrate or reconfigure.
How is Multidomain Enabled?
Automatically, when the first additional domain is connected.
What Happens to Records That Do Not Match Any Routing Rule?
They sync to the default domain.
Who Can Edit Egnyte Settings?
Users with the Egnyte Administrator permission set or full org admin rights.
Can the Domain’s Setting Name Be Renamed?
No. Domain settings cannot be renamed once created