Create up to 100 environments in your integrator.io account and switch between them, enable them, and disable them as your work requires. This article is for Production account owners and administrators, who are the only users who can create and manage environments. It covers creating an environment, switching between environments, enabling and disabling an environment, and reusing resources across environments. For the concepts behind environments and what they share, see Multiple environments overview.
Editions: Professional and Enterprise editions
Who can manage environments: Production account owners and administrators
Create an environment
Your first environment is always Production. Every environment you create afterward is a non-production environment, and new environments are disabled by default.
- Switch to your Production environment.
- Go to Account
, and then select Environments.
- Select Create environment.
- Complete the settings. Use a descriptive, unique name, such as NetSuite QA or NetSuite Development Sandbox rather than QA or Test. If you use API Management, also set the Environment prefix for APIM — see Use multiple environments with API Management.
Enable the environment when you're ready to use it. See Enable or disable an environment.
Switch between environments
Select your desired environment from the top bar in integrator.io. This automatically loads all resources for that environment. Note that you will only see environments you have permission to access.
Enable or disable an environment
Enable environments as you need them, and disable them to stop flows, revoke access tokens, and restrict user access. New environments are disabled by default, and you can't disable Production. If you've reached your enabled-environment limit, you're prompted to request an upgrade when you try to enable another one — see Monitor entitlements usage.
- Switch to your Production environment.
- Go to Account
, and then select Environments.
- Turn Status on or off for the environment.
Note: Resolve any pending invitations before you disable an environment.
When you disable an environment:
- All of its flows are disabled.
- All of its access tokens are revoked.
- All users lose access to it.
Disabling never deletes an environment's contents. Everything becomes available again when you enable it.
Clone resources between environments
Each environment keeps its own isolated resources, so a resource you build in one environment isn't available in another. To reuse work — for example, to promote an integration from a Development environment to Production — clone it into the target environment:
- Clone integrations and flows
- Clone exports
- Clone imports
- Account dashboard and integration dashboard
If you manage an integration's lifecycle across environments, you can pull changes from a source environment into your current one instead of cloning again. See Use multiple environments with Integration Lifecycle Management (ILM).