Multi-Region Workspace Synchronization
Overview
Multi-region synchronization keeps selected workspace settings consistent across Unified data regions (US, EU, AU).
You can manage it from:
Settings → Workspace → Multi-region synchronization
This feature is for workspace configuration. It does not copy your customers' integration data between regions.
Availability
- Multi-region synchronization is available only on the Scale plan.
- Only workspace admins can update workspace settings.
- Your workspace is billed once, in the region where synchronization was first turned on. API usage from all your synced regions is combined on that invoice.
How to turn it on
- Go to Settings → Workspace → Multi-region synchronization.
- First select Workspace. After Workspace is enabled, the full list of sync options appears.
- Select the options you want, then click Update.
| UI option | What it syncs |
|---|---|
| Workspace | General workspace settings, such as the workspace name and IP restrictions. |
| Workspace Secrets Manager | Workspace credentials, such as your Datadog API key, Secrets Manager configuration, and SAML configuration. Select this together with Workspace. |
| Workspace Integrations | Integrations that are enabled in this workspace. |
| Users | Workspace users. |
| Keys | Workspace API keys. |
| Notifications | Workspace notifications. |
Workspace Secrets Manager
By default, workspace credentials are not included when you enable Workspace sync. These include:
- Log and monitoring credentials, such as your Datadog API key and your AWS, Azure, GCP, Grafana, and ClickHouse logging settings
- Your Secrets Manager configuration (AWS, Azure, GCP, HashiCorp Vault, etc.)
- Your SAML configuration
To sync workspace credentials, select both:
- Workspace
- Workspace Secrets Manager
Use this when you want the same credentials to be available across your enabled regions.
What is synced
Multi-region synchronization can sync:
| Category | Synced data |
|---|---|
| Workspace | General workspace settings, such as IP restrictions, workspace name, etc. |
| Workspace Secrets Manager | Workspace credentials, such as your Datadog API key, Secrets Manager configuration, and SAML configuration. Synced when enabled together with Workspace. |
| Workspace Integrations | Integrations that are enabled in this workspace. |
| Users | Workspace users. |
| Keys | Workspace API keys. |
| Notifications | Workspace notifications. |
What is not synced
Multi-region synchronization does not sync:
| Not synced | Meaning |
|---|---|
| Connections | Individual customer connections are not copied between regions. |
| Webhooks | Webhook subscriptions, webhook events, and webhook delivery history are not copied by this setting. |
| API logs | API request logs are not copied by this setting. |
| Customer integration data | Contacts, jobs, employees, files, messages, tickets, and other third-party object data are not copied between regions. |
| Sandbox data | Sandbox records are not copied by this setting. |
| Billing records | Billing records are not copied by this setting. |
How updates sync
When you create, update, or delete a synced item in one region, Unified syncs that change to all your other regions. There may be a brief delay before all regions reflect the update.
If the same item is changed in two regions at about the same time, the most recent change wins.
Initial sync
When you enable a new sync option, Unified also syncs the existing records for that option.
For example, if you enable Users, existing workspace users are synced to your other regions.
If you enable Workspace Secrets Manager, make sure Workspace is also selected.
How to turn it off
- Go to Settings → Workspace → Multi-region synchronization.
- Unselect the options you no longer want to sync, then click Update.
To fully turn off multi-region synchronization, unselect all options and click Update.
Turning sync off stops future changes from syncing. It does not automatically delete settings that were already synced to other regions.
Important notes
Multi-region synchronization is intended for workspace setup and access configuration.
It should not be used to migrate customers' integration data, connections, webhook history, or logs.