Configuration management

As your workspace matures you’ll want to build changes safely in one place and deploy them to another — a sandbox and a production, or a template reused across organizations. Admin → Configuration does exactly that: every configuration change is tracked into a package, packages are exported and imported between workspaces, and every deployment can be rolled back.

Change tracking

Once you make a package active, every configuration change you make — record types, fields, forms, workflows, reports, dashboards, notification rules, groups, permissions, connectors, jobs, settings — is recorded into it automatically. Edit the same object five times and the package keeps one entry with its final state, so packages stay readable.

• The active-package banner at the top of the Configuration page shows where your changes are going; switch packages any time.
• A package’s contents are listed by domain — see at a glance that it touches 3 fields, 1 workflow and 2 reports.
• Changes made through the AI assistant are tracked too — approved proposals land in the active package like hand-made changes.

Exporting a package

1. Open the package, click Validate — missing dependencies (a form that needs a field not in the package) are flagged before they can bite.
2. Click Export — you get a single portable file with an integrity checksum.

Objects travel by name, not internal ID, so a package built in one workspace applies cleanly in another. Secrets are never exported — connector API keys, passwords and mail credentials are excluded by design; the import lists them as manual steps for an administrator to re-enter on the target.

Importing — always preview first

On the target workspace:

1. Import → upload the file.
2. Review the preview: what will be created, updated or is already identical, any missing dependencies, and the manual steps (secrets to re-enter, passwords to set).
3. Click Apply.

Nothing is applied without the preview and your confirmation, changes land in dependency order, and imports are repeatable — applying the same package twice is harmless.

Creating a sandbox from production

To stand up a test workspace that mirrors production, use the full-configuration export: it captures the entire current configuration — every type, field, form, workflow, report, rule — as one package. Import it into a fresh workspace and you have a faithful sandbox (configuration only — records don’t travel; import sample data separately). Build and test changes there in a package, then export just that package back to production.

Deployment history and rollback

Every apply is recorded in Deployment history with a snapshot of the configuration as it was before. If an import turns out wrong, Rollback restores that snapshot — the affected objects return to their pre-deployment state. Between preview, checksums, manual-step lists and rollback, moving configuration is a controlled release, not a leap of faith.