Safely build, test, and manage integrations without risking the stability of your live Production environment. Create up to 100 environments that you can switch between, enable, or disable as you need.
In legacy Production and Sandbox accounts, changes in one environment automatically impact the other because they share the same underlying resources. The multi-environment model solves this by providing isolated workspaces for development, QA, and staging. Decoupling your integrations, flows, connections, and scripts allows you to build and test freely without risking your live production data. For the concepts behind multiple environments and to understand which resources are shared, see Multiple environments overview.
What editions is this available on? Professional and Enterprise editions
Who has access? Production account owners and admins
Your first, original environment is always your Production environment. Every environment you create afterward is a non-production environment, and all new environments are disabled by default. You can create up to 100 environments in total.
- Go to Account
, and then select Environments.
- Select + Create environment.
- Complete the fields to create your environment. See also Use multiple environments with API Management and Use multiple environments with Integration Lifecycle Management (ILM).
Tip: Use descriptive names. For example, use NetSuite QA or NetSuite Development Sandbox rather than just QA or Test. Keep in mind that environment names must be unique within your account.
To move between environments, select the environment from the list at the top of the page. Account owners see a list of all their environments; shared users see the accounts and environments they've been invited to (see Invite users and manage access to an account or environment). Switching environments loads that environment's resources.
Enable or disable an environment
Keep your flows and tokens securely locked down until you are ready. You can enable environments as you need them and disable them to halt flows, revoke access tokens, and restrict user access—giving your team absolute control over testing boundaries and system security.
New environments are disabled by default, and you can't disable your Production environment. If you've reached your enabled-environment limit and try to enable a new environment, you'll be prompted to request an upgrade — see Monitor entitlements usage.
- Go to Account
- Turn on or off the Status to enable or disable an environment.
Resolve any pending invitations before disabling the environment.
When you disable an environment:
- All flows are disabled.
- All access tokens are revoked.
- All users' access to the environment is disabled.
Clone resources between environments
Because each environment keeps its own isolated resources, a resource you build in one environment isn't available in another. To reuse work — for example, to promote an you developed in a Development environment into Production — you clone it into the target environment. See the following:
If you're managing an integration's lifecycle across environments, you can pull changes from a source environment into your current one rather than cloning again. Selecting the source environment when pulling is covered in Use multiple environments with Integration Lifecycle Management (ILM).