Developer Sandboxes installation and configuration

concept brazil Updated Oct 26, 2026 3 min read dsb-configuring-landing.md
Raw file servicenow.com

Developer Sandboxes installation and configuration covers Developer Sandboxes on your instance. Review entitlements, install the plugins, assign licenses, and look up the roles, tables, and properties that control how sandboxes work.

Configuration overview

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

    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

    Review the prerequisites, install the plugins, and set the required properties.

  3. Enable SSO if needed

    If you use single sign-on (SSO), set the properties on the base instance that let developers use SSO to access sandboxes.

  4. Assign licenses to instances

    Assign purchased sandbox packs to non-production instances from App Engine Management Center (AEMC) without opening a support case. You need access to AEMC with the sandbox_license_admin role role to open the license assignment page, and the app_engine_admin role is required.

Additional configuration information

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

  • Developer Sandboxes domain separation

    Set up domain separation on the base instance before sandboxes are created, so that sandboxes inherit the domains you define.

  • Components installed with Developer Sandboxes

    Look up the roles, plugins, and tables that are installed with Developer Sandboxes.

  • Properties installed with Developer Sandboxes

    Look up the system properties that govern sandbox behavior, such as node counts, table configuration, and data copy settings.

  • Developer Sandboxes entitlements
    Your company's entitlements determine whether you have access to Developer Sandboxes.

  • Developer Sandboxes installation
    Developer Sandboxes is installed on your instance, with licenses from a pack assigned by your admin. Review prerequisites and plugin requirements before installation begins.

  • Single sign-on for Developer Sandboxes
    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.

  • License assignment
    License assignment in App Engine Management Center (AEMC) lets Developer Sandboxes admins distribute purchased sandbox packs across non-production instances without opening a support case. Each pack contains 10 sandboxes, and assignments are managed from a license management instance.

  • Developer Sandboxes domain separation
    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.

  • Components installed with Developer Sandboxes
    Several types of components are installed with activation of Developer Sandboxes, including tables and user roles.

  • Properties installed with Developer Sandboxes
    The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.

Parent Topic:Developer Sandboxes

Keywords configureinstalldeveloper sandboxessandbox license assignmentsandbox properties
Search documentation
Search document titles and file paths on the brazil branch