composer

Testing in a sandbox

Use a sandbox tenant to iterate on Composer changes without touching production records.

6 min read · 1 sections

Sandbox lifecycle

Owner or tenant-admin provisions a sandbox via /settings/tenant → Sandboxes.
Sandboxes are isolated — their own DB schema, own users, own branding.
Compose, iterate, seed fake data — none of it is visible to your production users.
Export the Composer definition from the sandbox.
Import into production. A diff view shows exactly what will change.
Publish. Rollback is available for 14 days.