Articles in this section

Create and manage non-production environments

Warning

You must be an account owner or administrator in the Production environment to create or manage environments.

 

Create a new environment

Warning

This feature is available in accounts created after January 28, 2025, and accounts created before January 28, 2025 with no Sandbox subscription. Multiple environments in accounts created before January 28th with a sandbox subscription will be available in March 2025.

Your first, original environment is always your Production environment. Any newly created environments are considered non-production environments. You must be in your Production environment to create a new environment. Additionally, all newly created environments are disabled by default. 

  1. Click your account profile at the upper right-hand corner of the page.

    Account_highlight.png
  2. Click Environments from the dropdown.

    Environments_account_dropdown.png
  3. Click + Create environment on the right-hand side of the page.

    Environments_create_env.png
  4. Add a Name and Description.

    Tip

    Be descriptive with your environment's name and description. For example, try NetSuite QA or NetSuite Development Sandbox instead of just QA or Test.

    Create_environment_window.png
  5. If you're using API Management, add your Environment prefix for APIM. This prefix is used to generate the Developer portal and API gateway URLs. You can change this later, but it may cause issues, as your API consumers are not notified of the change. Learn more about API Management and non-production environments.

Enable or disable an environment

To enable or disable an environment, use the toggle on the right-hand side of the environment name. You cannot disable your Production environment. Any newly created environments are disabled by default.

Environments_status_highlight.png

When an environment is enabled, the following occurs:

  • No flows are enabled.

  • No access tokens are updated.

  • Administrative users are enabled only if they were previously enabled.

  • No non-administrative users are enabled.

When an environment is disabled, the following occurs:

  • All flows are disabled.

  • All access tokens are revoked.

  • All users' access to the environment is disabled.

    Note

    You must resolve any pending invitations before disabling the environment.

Environment resources

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 are only available within the prod environment. Templates are available throughout all environments. Account and integration specifics are also based on the environment.

Learn more about:

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.