Skip to main content

Sandbox Workspace

A Sandbox workspace is a separate workspace linked to a paying ("parent") workspace, for testing new setups, automations, or configurations in a clean environment.

Key characteristics​

  • One per paying workspace — each paying workspace owner can create only one.
  • Starts completely empty — nothing is copied from the parent workspace on creation.
  • Same limits and credits as the parent, but not shared — e.g. if the parent has a limit of 1,000 automations, the sandbox also gets 1,000, for 2,000 available in total across both.
  • Fully isolated — activity in the sandbox doesn't affect the parent's data, usage, or limits.

Typical uses: testing new automations or workflows, trying configurations before applying them to production, validating changes without risking live data.

Syncing a sandbox from production​

note

Production-to-sandbox data sync may be available as a paid add-on.

A sync pulls a representative slice of production's structure and data into the sandbox, so it mirrors production without carrying its full volume.

What gets copied: structure (spaces, types with their attributes and icons, workflows with states/transitions/conditions), a sample of objects per type with their attribute values, automation rules, and sites (apps).

Configurable per sync, via checkboxes framed as what to include rather than what to skip: Sync objects (checked by default — unchecking it syncs structure only), Sync automations, and Sync sites (both unchecked/opt-in by default, since copying them is a heavier action).

Object limit: up to 50 objects per type, not 50 total — a workspace with many types can sync more than 50 objects overall.

Behavior notes:

  • Synced automation rules are always created disabled, so nothing fires unexpectedly.
  • The workspace owner or an admin can run a sync.
  • Every space in the parent workspace is copied — including ones the syncing user can't open — with each copied space carrying over its original permissions. Access in the sandbox still follows those permissions, so a sync doesn't expose anything the user couldn't already see.
  • A sync wipes the sandbox's existing data first, then copies fresh data from production.

Find this on the sandbox workspace's Settings > General page, as a Sandbox section row visible only there, and only to a workspace owner or admin.

Sync from production workspace
Replace this sandbox with a fresh copy of the production workspace's configuration and data.
Sync from production
Sync from production workspace?
This replaces all data in this sandbox with a fresh copy from the production workspace. This cannot be undone.
Sync objects
At most 50 objects per type are copied.
Sync automations
Copied automations are created disabled.
Sync sites