Multiple environments turn your integrator.io account into separate workspaces for development, QA, and staging alongside Production. Each environment keeps its own integrations, flows, connections, and scripts, so a mistake in a non-production environment can't reach your live data. This article explains what environments are, what they share, and where to go to create and use them. It's for account owners and administrators on Professional and Enterprise editions.
Editions: Professional and Enterprise editions
Who can manage environments: Production account owners and administrators
Production and non-production environments
Every account starts with one environment, Production. Production is created automatically when the account is set up, is enabled by default, and can't be renamed or disabled. Every environment you add afterward is a non-production environment that you can name, enable, and disable to fit your workflow. You create and manage environments from Production, and the Production owner and administrators automatically hold the same roles in every environment. See Create and manage multiple environments.
The environment switcher
The environment you're working in is shown in the top bar of integrator.io. To work in a different environment, select Production, Sandbox, or any environment you've created from the top bar. Account owners see every environment in the account; other users see only the environments they've been invited to. Switching loads that environment's resources.
See Invite users and manage access to an account or environment.
Entitlements
You can create up to 100 environments. Environments share your account's license rather than carrying separate costs, and each one has the same entitlements as Production: your available flows, endpoints, trading partners, and on-premise agents match Production automatically. See Manage your Celigo subscription.
Global connector licenses also carry across environments. A global license can be used in more than one environment at a time, and its expiration date is tied to your integrator.io account rather than to a single environment.
If you have more environments than licenses (for example, five environments and three licenses), you can upgrade your subscription or disable an active environment and enable a different one. If you exceed your environment limit, your oldest non-production environments are disabled first. Disabling an environment never deletes its contents — flows, connections, and other resources pause and become available again when you enable the environment. See Create and manage multiple environments.
Resource isolation
Resources you create in an environment — on-premise agents, imports, exports, connections, scripts, API tokens, and so on — exist only in that environment. A flow built in a Development environment doesn't appear in Production, and a connection created in Production isn't available in a QA environment. To reuse a resource in another environment, clone it. See Create and manage multiple environments.
A few things are shared across all of your environments:
- Integration app licensing — Integration apps use a single license across your account. Purchase one integration app license and install it in any or all of your environments; you're charged by the number of enabled integration app flows, not by how many times you install the app. See Install and manage integration apps across environments.
- Marketplace templates — Available in every environment.
Account-level settings that apply to every environment
Some settings are managed in Production and then apply to your non-production environments automatically, so your environments stay consistent without separate configuration:
- Account time zone
- Data retention period
- Error management settings
- Security requirements, such as single sign-on (SSO) and multifactor authentication (MFA)
For how SSO, MFA, and data retention cascade, see Manage environment security.
Legacy Production and Sandbox accounts
Accounts created before the multiple-environment structure have a legacy Production and Sandbox pair that share the same underlying resources. A resource you create, edit, or delete in one — including API tokens, on-premise agents, stacks, and iClients — is immediately reflected in the other. If the top bar of integrator.io shows a Production | Sandbox control instead of the Environment list, your account is still on the legacy structure. Celigo prompts the account owner and administrators to upgrade. See Upgrade to the multiple-environment structure.