Warning
You must be an account owner or administrator in the Production environment to create or manage environments.
Legacy production and sandbox licenses
In legacy Production and Sandbox environments, changes in one environment affect both environments. The Production and Sandbox environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other.
This includes connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment.
This behavior doesn't apply to accounts on the multi-environment license, where each environment maintains its own isolated resources.
Migrations from the legacy Production/Sandbox license to the new multi-environment license are underway. Your account has not migrated to the new multi-environment license if you can toggle between environments.
Various security and data retention requirements can be enabled.
Require single sign-on (SSO) or multifactor authentication (MFA) will be automatically enabled based on the production environment settings. The account owner or administrator must first enable any security features in the production environment. After they've been enabled in production, non-production environment admins can modify security features per environment. For MFA authentication specifically, you must set the permissions requirements in the production environment (e.g., 30-day device trust), which will cascade down to users in other environments. All environments can allow either SSO or MFA, not both simultaneously.
If you're using or want to extend your data retention period, it must be set by an owner or admin directly in the production environment. After being set for prod, the retention period cascades to all environments.
Learn more about the benefits of retaining your log and error data.