Environments help teams separate test automation from production workflows.
Open Environments
Go to Settings → Environments in the sidebar (SETTINGS section).
Recommended layout
| Environment | Purpose |
|---|---|
| Development | Experiment with workflows and connectors using sandbox credentials |
| Staging | Validate changes with production-like data |
| Production | Live automations that affect customers or revenue systems |
Team access
Use Settings → Team Members to control who can edit workflows and connectors. Pair environment separation with role-based access for safer releases.
API
Environment metadata is available at /api/environments for org admins automating setup.
Legacy naming
Older docs and UI copies may say "Workspaces." The product label is now Environments; routes and APIs may still use environment or legacy identifiers internally.