--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Installing # Installing Developer Sandboxes {#ariaid-title1} * Release version: Australia * * Updated July 23, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Installing Developer Sandboxes Developer Sandboxes is a paid ServiceNow feature that enables creation and management of sandbox instances for development purposes. Installation requires assistance from your ServiceNow account team and is performed on your production or clone source instance to maintain entitlement during cloning. Sandboxes are instance-specific and cannot be moved between instances. Show full answer Show less ## Prerequisites and Installation Process * **Entitlement Check:** Verify access to Developer Sandboxes through your entitlements before proceeding. * **Instance Requirements:** Must use a non-production instance running ADCv3 (Application Delivery Controller version 3). If not on ADCv3, the instance will be upgraded during setup. * **Sandbox Packs and Nodes:** Sandboxes are sold in packs of 10, with a minimum purchase of one pack per instance. Each sandbox runs on its own app-node, so purchasing 10 sandboxes adds 10 nodes to your instance. Multiple packs can be split across different instances, but each instance requires a minimum of 10 sandboxes. * **Self-hosted Instances:** Not supported by default; custom networking and routing configurations are necessary if you choose to enable sandboxes on self-hosted instances. ## Requesting Installation and Support To install Developer Sandboxes after procurement, submit a case with Now Support specifying your instance name and the number of licensed sandboxes. If your instance is in a regulated environment, consult ServiceNow Support for additional guidance. ## Enabling Single Sign-On (SSO) Developers can access sandboxes using either instance credentials or SSO. To enable SSO, configure these properties on the base instance: * Disable ACR: **glide.sso.acr.enable = false** * Enable SSO: **glide.authenticate.multisso.enabled = true** ## Key Takeaways for ServiceNow Customers * Ensure you have proper entitlements and procurement completed before installation. * Developer Sandboxes are added as additional nodes on your instance, so capacity planning is essential. * Contact Now Support to complete installation and configuration. * SSO setup requires specific system properties to be adjusted for seamless developer access. * Sandbox instances are tied to specific instances and cannot be transferred. Developer Sandboxes is installed on your instance with assistance from your ServiceNow account team. ## Requesting Developer Sandboxes installation {#dev-sbx-installing__section_iw5_w4h_lgc} Check your entitlements to determine whether you have access to Developer Sandboxes. For more information, see [Developer Sandboxes entitlements](https://www.servicenow.com/docs/YZOONAc9YFBLi_mDhQOr1Q "Your company's entitlements determine whether you have access to Developer Sandboxes."). Developer Sandboxes is a paid feature and is enabled only after procurement is complete. To install Developer Sandboxes once you're entitled, open a case with Now Support specifying the instance name and licensed number of sandboxes. Note: * If your instance is in a regulated environment, check with ServiceNow Support for more information about support for Developer Sandboxes. * The Developer Sandboxes plugin should be installed in your production instance, or any clone source to ensure that cloning a sandbox instance correctly maintains entitlement. {#dev-sbx-installing__ul_ecp_hcj_zjc} ## Prerequisites for installing Developer Sandboxes {#dev-sbx-installing__section_zl1_bx4_3hc} You must have the following to install Developer Sandboxes: * A non-production instance * The instance is on ADCv3 (Application Delivery Controller version 3) Note: If the instance is not on ADCv3, it will be moved it as part of the setup. * Yokohama or higher {#dev-sbx-installing__ul_fqr_hx4_3hc} ## Instances and sandboxes {#dev-sbx-installing__section_ktk_bxq_jhc} Sandboxes are instance-specific, which means that you can't move a sandbox from one instance to another. If a new instance needs to be sandbox enabled, it will be a net new order. Each sandbox is hosted in its own app-node. Therefore, a key part of the setup is adding the required number of additional nodes on the instance. For example, to support 10 sandboxes, 10 new nodes would be added to an instance. Developer Sandboxes are available in packs of 10. When you buy two or more packs, you can split the pack between different instances. To do so, open a request with Now Support for each instance. Note: The minimum is one pack of sandboxes (10) per instance. For example, If you buy two packs, you can't split them 5-15. Each instance must have at least 10 sandboxes. Developer Sandboxes does not support self-hosted instances by default, though you can set up your own networking and routing changes to support sandboxes. For more information on sandboxes and instances, see [General guidelines and use cases for Developer Sandboxes](https://www.servicenow.com/docs/xqj28So6zTrIfsa20wvtGQ "Follow some general guidelines to ensure you're optimizing your use of sandboxes."). ## Contact Now Support to finish installation {#dev-sbx-installing__section_e2s_ymv_bhc} The number of available sandboxes on an instance is defined by the number of purchased entitlements. You must contact Now Support to open a case to finish installing and configuring Developer Sandboxes. ## Enabling SSO {#dev-sbx-installing__section_qr2_z4h_lgc} Developers can access sandboxes using instance credentials as well as Single Sign-On (SSO). The following properties must be set in the base instance before developers can use SSO to access sandboxes: * Disable ACR: `sys_property glide.sso.acr.enable=false` * Enable SSO: `glide.authenticate.multisso.enabled = true` {#dev-sbx-installing__ul_bjw_2ph_lgc}