---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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


---

# Install and configure

# Developer Sandboxes installation and configuration {#ariaid-title1}

Release version: Australia  
Updated October 26, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Developer Sandboxes installation and configuration covers Developer Sandboxes on your instance. Review entitlements, install the plugins, and look up the roles, tables, and properties that control how sandboxes work.

## Configuration overview {#dsb-configuring-landing__cf-config-parent-checklist}

Complete these tasks in the following order. You must install Developer Sandboxes and set up the instance before you can assign licenses to it.

1. [Review your entitlements](https://www.servicenow.com/docs/z44OpXdvOXuh7RBHYFqAyw "Your company's entitlements determine whether you have access to Developer Sandboxes.")

   Review the entitlements that determine whether you have access to Developer Sandboxes, how sandbox packs are sized, and how many sandboxes an instance can have.
2. [Install Developer Sandboxes](https://www.servicenow.com/docs/G5m7ZZKu2ZhCi_1SPZ~cKA "Developer Sandboxes is installed on your instance with assistance from your ServiceNow account team.")

   Review the prerequisites, install the plugins, and set the required properties.
3. [Enable SSO if needed](https://www.servicenow.com/docs/1AMU7_VdIIoM6sK3CO6AEw "Sandboxes use the same login credentials as the base instance, including single sign-on (SSO) when it's enabled there. Set the required properties on the base instance so developers can use SSO to access sandboxes.")

   If you use single sign-on (SSO), set the properties on the base instance that let developers use SSO to access sandboxes.
{#dsb-configuring-landing__cf-config-parent-tasks-ol}

## Additional configuration information {#dsb-configuring-landing__cf-config-parent-reference}

Use these topics to set up related features and look up what is installed with Developer Sandboxes.

* [Developer Sandboxes domain separation](https://www.servicenow.com/docs/YD14GaI6PrEWNcicatH3jw "Domain separation is supported for Developer Sandboxes. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.")

  Set up domain separation on the base instance before sandboxes are created, so that sandboxes inherit the domains you define.
* [Roles and tables installed with Developer Sandboxes](https://www.servicenow.com/docs/ruLnnnY8tziXC3TkwWQ95g "Several types of components are installed with activation of Developer Sandboxes, including tables and user roles.")

  Look up the roles, plugins, and tables that are installed with Developer Sandboxes.
* [Properties installed with Developer Sandboxes](https://www.servicenow.com/docs/pLCFXKDlzI9mAmtFZdTjEA "The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.")

  Look up the system properties that govern sandbox behavior, such as node counts, table configuration, and data copy settings.
{#dsb-configuring-landing__cf-config-parent-tasks-ul}