Articles in this section

Learn about non-production environment licenses, entitlements, and resources

What editions is this available on? Professional and Enterprise editions

Who has access? Production account owners and admins

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.

Toggle to Sandbox environment.png

Environment entitlements and licenses

If you are an account owner or administrator in the Production environment, you can create or manage additional environments. However, you may need to request an upgrade to activate a new environment. Environments are available with no upgrades to users on the Enterprise plan.

If you have an endpoint subscription or are not on an Enterprise plan, you can create a new environment, but you'll have to request an upgrade to enable it. Requesting an upgrade is easy through the platform. Simply create an environment and attempt to enable it. A pop-up will appear, and you can click the link to request the update directly from the Celigo platform. You can also click Request upgrade in your account settings' Environments tab.

You can create up to 100 environments (including your existing Production environment), but you'll need licenses for each environment. For example, if you create five environments with only three licenses, you must choose which three environments you want to enable. Of course, you can disable one environment and enable another anytime.

Your newly created environment will have the same license entitlements as your Production account. For example, the number of flows, endpoints, trading partners, and agents will all be the same for Production and other environments.

Environment resources

In multi-environments, resources like imports, exports, connections, scripts, API tokens, etc., created in an environment are only accessible in that environment. However, you can clone resources to share between environments. Integration apps migrated to the new multi-environment license are available throughout your environments. Templates are available throughout all environments. Account and integration specifics are also based on the environment.

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.

Toggle to Sandbox environment.png

Learn more about:

Downgrade your environment licenses

You can downgrade the number of environment licenses you have at any time. After downgrading, your oldest environments are disabled first. For example, if you have licenses for three environments and then downgrade to two environments:

  • Environment 1 on January 1st

  • Environment 2 on January 2nd

  • Environment 3 on January 3rd

Environment 1 will be disabled automatically since it's the oldest environment. Flows, connections, and other environment details are never deleted. They are only disabled. Learn more about what happens when you disable an environment.

Important

Your Production environment will never be disabled. Only non-production environments are disabled.