Allocate a sandbox
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.
[Omitted video] Description: Demo of allocating 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. By default, a pooled sandbox that stays unclaimed for 24 hours is retired and replaced with a new one. For more information, see Properties installed with Developer Sandboxes.
Procedure
-
Navigate to All > Sandbox Management > Sandbox Management Home.
-
Select Allocate sandbox.
[Omitted image "dev-sbx-home-allocate-btn.png"] Alt text: Allocate sandbox button on the home dashboard
-
On the form, fill in the fields.
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.The name must be 1 to 20 characters long and can contain lowercase letters, numbers, and hyphens. The name must include at least one letter and can't start or end with a hyphen. [Omitted image "dev-sbx-allocate-modal.png"] Alt text: Fill in the Allocate Sandbox form
-
Select Allocate.
[Omitted image "dev-sbx-allocate-requested.png"] Alt text: Provisioned sandbox initializing
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 [Omitted image "dev-sbx-refresh-icon.png"] Alt text: to see updates to the Sandboxes list.The record for the sandbox appears in the list as Initializing until the sandbox is ready.
After allocation, developers can access their sandbox in the following ways:
- Select the sandbox name on the Sandbox Management Home page.
- Copy the sandbox URL from the context menu and paste it in a browser.
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 using the same credentials. For information on enabling SSO, see Single sign-on for Developer Sandboxes.
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.
Parent Topic:Administering Developer Sandboxes
---
title: Allocate a sandbox
description: Allocate sandboxes to your development teams so they can start using them for development.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/application-development/developer-sandboxes/allocating-sandboxes.html
release: brazil
product: Developer Sandboxes
classification: developer-sandboxes
topic_type: task
last_updated: "2026-10-20"
reading_time_minutes: 2
breadcrumb: [Administering, Developer Sandboxes, Build, AI Workflow Factory Prime, Agentic app development, Building applications]
---
# Allocate a sandbox
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.
\[Omitted video\] Description: Demo of allocating 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. By default, a pooled sandbox that stays unclaimed for 24 hours is retired and replaced with a new one. For more information, see [Properties installed with Developer Sandboxes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/application-development/developer-sandboxes/dsb-properties-installed.md).
## Procedure
1. Navigate to **All** > **Sandbox Management** > **Sandbox Management Home**.
2. Select **Allocate sandbox**.
\[Omitted image "dev-sbx-home-allocate-btn.png"\] Alt text: Allocate sandbox button on the home dashboard
3. On the form, fill in the fields.
|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.The name must be 1 to 20 characters long and can contain lowercase letters, numbers, and hyphens. The name must include at least one letter and can't start or end with a hyphen.|
\[Omitted image "dev-sbx-allocate-modal.png"\] Alt text: Fill in the Allocate Sandbox form
4. Select **Allocate**.
\[Omitted image "dev-sbx-allocate-requested.png"\] Alt text: Provisioned sandbox initializing
## 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 \[Omitted image "dev-sbx-refresh-icon.png"\] Alt text: to see updates to the Sandboxes list.The record for the sandbox appears in the list as **Initializing** until the sandbox is ready.
After allocation, developers can access their sandbox in the following ways:
- Select the sandbox name on the Sandbox Management Home page.
- Copy the sandbox URL from the context menu and paste it in a browser.
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 using the same credentials. For information on enabling SSO, see [Single sign-on for Developer Sandboxes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/application-development/developer-sandboxes/dev-sbx-sso.md).
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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/application-development/developer-sandboxes/dsb-update-sets.md).
**Parent Topic:**[Administering Developer Sandboxes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/application-development/developer-sandboxes/administering-sandboxes.md)
| title | Allocate a sandbox |
| description | Allocate sandboxes to your development teams so they can start using them for development. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/application-development/developer-sandboxes/allocating-sandboxes.html |
| release | brazil |
| product | Developer Sandboxes |
| classification | developer-sandboxes |
| topic_type | task |
| last_updated | 2026-10-20 |
| reading_time_minutes | 2 |
| breadcrumb | AdministeringDeveloper SandboxesBuildAI Workflow Factory PrimeAgentic app developmentBuilding applications |