> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/sandbox-management/sandboxes/creating-a-sandbox.md).
# Creating a Sandbox
##  Overview
This article explains how to create a Salesforce sandbox from a source organization in Sandbox Management, without a template, and connect it to your tenant. When the sandbox is connected, it is added to Global Settings as an organization with the Sandbox Management app assigned.
Sandbox Management uses Salesforce's standard sandbox process. When you create a sandbox, Salesforce creates it with one of your Salesforce org's sandbox licenses, and the new sandbox appears in Salesforce Setup on the **Sandboxes** page, alongside your other sandboxes.
To apply a template while you create a sandbox, see the following article.
* [Creating a Sandbox with a Template](/sandbox-management/sandboxes/creating-a-sandbox-with-a-template.md)
{% hint style="info" %}
#### Before You Begin
The organization you copy must be connected in Global Settings and have the Sandbox Management app assigned. Only organizations with the app assigned appear in the **Source organization** list.
* [Adding Organizations to Sandbox Management](/sandbox-management/getting-started/adding-organizations-to-sandbox-management.md)
{% endhint %}
## Creating a New Sandbox
{% stepper %}
{% step %}
### Open the Create Sandbox Form
1. Click **Sandboxes** from the left sidebar menu.
2. Click **Create Sandbox**.
{% endstep %}
{% step %}
### Enter the Sandbox Details
1. Enter a **Name** for the sandbox.
{% hint style="info" %}
#### Sandbox Names
A sandbox name can contain only letters and numbers, can't start with a number, and can be up to 10 characters long.
{% endhint %}
2. Click the **Source organization** dropdown menu.
3. Select the organization to copy.
4. Click the **Sandbox type** dropdown menu.
5. Select **Developer**, **Developer Pro**, **Partial**, or **Full**.
{% hint style="info" %}
#### Sandbox Licenses
Each sandbox type uses one of your Salesforce org's sandbox licenses. Select a type that your Salesforce org has an available license for.
{% endhint %}
6. Click the **Sandbox access** dropdown menu.
7. Select the public group whose members can access the sandbox. The list shows the public groups in the source organization. To create a public group for sandbox access, see [Determine Who Has Sandbox Access](https://help.salesforce.com/s/articleView?id=sf.data_sandbox_selective_access.htm\&type=5) in Salesforce Help.
8. (Optional) Click the **Apex Class** dropdown menu and select an Apex class to run after the sandbox is created. The class must implement Salesforce's `SandboxPostCopy` interface. The list shows every Apex class in the source organization, and a class that doesn't implement the interface doesn't run.
{% hint style="info" %}
#### Template
This article covers creating a sandbox without a template, so it skips the **Template** field. See the following article for instructions on creating a sandbox with a template.
* [Creating a Sandbox with a Template](/sandbox-management/sandboxes/creating-a-sandbox-with-a-template.md)
{% endhint %}
9. Click **Create**.
{% endstep %}
{% step %}
### Monitor the Sandbox Creation
The **Sandboxes** list doesn't update on its own, so you need to refresh it to see the sandbox's progress.
{% hint style="info" %}
#### Creation Time
A new sandbox takes about a minute to appear in the **Sandboxes** list. Creating a sandbox can take from several minutes to several days, depending on the size of your Salesforce org and the sandbox type.
{% endhint %}
1. Click the refresh icon to the right of the search bar to update the list.
2. While Salesforce is creating the sandbox, its **Status** shows **Creating** and its progress.
3. When the **Status** changes to **Ready To Connect**, click the sandbox.
{% endstep %}
{% step %}
### Log In to the Sandbox
{% hint style="info" %}
#### Log In Before You Connect
Before you click **Connect**, log in to the new sandbox as the dedicated administrator user you will connect with. Salesforce may ask you to set up a passkey or an authenticator app the first time this user logs in. Completing this first makes the connection process smoother. To learn more about the dedicated administrator user, see the following article.
* [Creating a Dedicated Salesforce User](/global-settings/environment/organizations/creating-a-dedicated-salesforce-user.md)
{% endhint %}
1. Click the sandbox's login URL under its name to copy the link.
2. Open a new browser tab and paste the login URL into the address bar.
3. Enter the **Username** and **Password** of the administrator user.
4. Click **Log In to Sandbox**.
5. If Salesforce asks you to create a passkey, click **Create Passkey** and follow the prompts.
6. Return to Sandbox Management.
{% endstep %}
{% step %}
### Connect the Sandbox
1. Click **Connect**.
2. Enter the **Username** of the same administrator user.
3. Click **Log In to Sandbox** and complete the login.
4. Click **Allow**.
{% hint style="warning" %}
#### Log In to the Correct Sandbox
Log in with a user from the sandbox you are connecting. If the login fails, or you log in to a different sandbox, the organization is added to Global Settings as **Inactive** and the sandbox doesn't connect. To try again, delete the organization in Global Settings, and then click **Connect** in Sandbox Management again.
* [Deleting an Organization](/global-settings/environment/organizations/deleting-an-organization.md)
{% endhint %}
{% endstep %}
{% step %}
### Review the Connected Sandbox
When the connection completes, the sandbox is added to Global Settings as an organization, with the **Dev** environment and the Sandbox Management app assigned. The organization has the same name as the sandbox.
1. Global Settings opens to the **Organizations** page, where you can view the new organization.
2. In Sandbox Management, the sandbox's **Status** changes to **Ready**.
3. Click the sandbox to view its details.
{% hint style="info" %}
#### Change the Environment or Apps
To change the organization's environment or assign other apps, update the organization in Global Settings.
* [Update an Organization Environment](/global-settings/environment/organizations/update-an-organization-environment.md)
* [Assigning an App to an Organization](/global-settings/environment/organizations/assigning-an-app-to-an-organization.md)
{% endhint %}
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/sandbox-management/sandboxes/creating-a-sandbox.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
