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.
Procedure
Navigate to All > Sandbox Management > Sandbox Management Home.
Select Allocate sandbox.
Allocate sandbox button on the home dashboard
- On the form, fill in the fields.
| Field | Description |
|---|---|
| Allocate to | User that owns the sandbox. |
| Sandbox template | Template selected for the sandbox.For information on configuring templates to generate reusable data, see Using sandbox templates. |
| Sandbox alias | Name that's used in the unique URL for the sandbox. |
Fill in the Allocate Sandbox form
- Select Allocate.
Provisioned sandbox initializing
Result
Developer Sandboxes starts the process of provisioning the sandbox.
Note: It can take between 10 minutes and two hours for a sandbox to be provisioned, depending on the size of the tables used in the template. 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 pre-pending the Sandbox alias value to the instance name followed by devsandboxes. For example, https://samsbox.[instance].devsandboxes.servicenow.com.
Sandbox users use the same login credentials for their sandbox as the base instance. If you use Single Sign-On (SSO) for login, when you enable it to connect to your account on the base instance, Developer Sandboxes authenticates using the same mechanism and credentials as the base instance. For information on enabling SSO, see Installing Developer Sandboxes.