---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Allocate a sandbox

# Allocate a sandbox {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Allocate sandboxes to your development teams so they can start using them for development.

## Before you begin

You can watch a short video on how to allocate a sandbox.

Role required: admin or sandbox_manager

## About this task

You can allocate a sandbox at the beginning of a story or during the project planning process.

When you allocate a sandbox, you claim one from a pre-created pool rather than waiting for a new instance to be provisioned. This makes sandboxes available faster, so you can start working sooner.  
Note:  
Because pooled sandboxes are pre-created, they may be out of date from the current base instance state, but are refreshed every 24 hours.

## Procedure

1. Navigate to AllSandbox ManagementSandbox Management Home.
2. Select Allocate sandbox.  
   Figure 1. Developer Sandboxes home
3. On the form, fill in the fields.  
   {#allocating-sandboxes__table_r2b_zqk_fcc__entry__2}

   | Field | Description |
   |-|-|
   | Allocate to | User that owns the sandbox. |
   | Sandbox alias | Name that's used to identify the sandbox, for example, in the sandbox management table. The name is configurable, but you can't change the URL. |
   [ ]

   {#allocating-sandboxes__table_r2b_zqk_fcc} Figure 2. Allocate Sandbox details
4. Select Allocate.  
   Figure 3. Sandbox initializing after allocation

## Result

Developer Sandboxes starts the process of provisioning the sandbox.  
Note:  
Sandboxes from the pool are allocated quickly. If the pool is exhausted, it can take between ten minutes and two hours to allocate a sandbox. You can select the refresh icon ![]() to see updates to the Sandboxes list. The record for the sandbox appears in the list as Initializing until the sandbox is ready.  
Once allocated, developers can access their sandbox by one of two ways:

* Selecting the sandbox name on the Sandbox Management Home page.
* Using the context menu and copy the URL to the clipboard and paste it to the browser.
{#allocating-sandboxes__ul_hyj_btx_gkc}

Sandbox users use the same login credentials for their sandbox as the base instance. If you use Single Sign-On (SSO), enabling it on the base instance also authenticates Developer Sandboxes \[var.developer-sandboxes-long\] using the same credentials. For information on enabling SSO, see [Installing Developer Sandboxes](https://www.servicenow.com/docs/e5dfK0SZoIt12DNp0VE_WA "Developer Sandboxes is a installed on your instance, with licenses from a pack assigned by your admin. Review prerequisites, plugin requirements, and SSO configuration before installation begins.").

Two automatically created update set sources enable you to retrieve, preview, and commit completed update sets between the sandbox and base instance using the standard update set process. For more
information, see [Update sets transfer between sandboxes and base instance](https://www.servicenow.com/docs/NeGxMQKQ1uSdXXBH4QYzDg "When a sandbox is ready, update set sources are automatically created on both the sandbox and the base instance, enabling transfers in either direction without manual configuration.").

*[\>]: and then