> 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/templates/creating-a-template.md).
# Creating a Template
##  Overview
This article explains how to create a template in Sandbox Management. A template is a sequence of steps that runs after a sandbox is created or refreshed, so every sandbox you create with it is set up the same way.
A template has four stages, which always appear in the same order: **Backup**, **Post-config Steps**, **Data Migration**, and **Flosum Topology**. Each stage contains one or more steps that you turn on with a toggle. This article creates a template that populates a sandbox with data and adds the sandbox to your Flosum topology, using the **Data Migration** and **Connect to Flosum Topology** steps.
To use your template when 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 **Data Migration** step uses a Data Migrator template to choose which records to copy into the sandbox. You can use one of Data Migrator's system templates or create your own before you start.
* [Creating a Template](/data-migrator/templates/template-designer/creating-a-template.md)
{% endhint %}
## Creating a New Template
{% stepper %}
{% step %}
### Open the Create Template Form
1. Click **Templates** from the left sidebar menu.
2. Click **Create Template**.
3. Enter a **Name** for the template.
4. Click **Create**.
{% endstep %}
{% step %}
### Configure the Backup Step
The **Metadata** step backs up the sandbox's current metadata before a refresh. This example doesn't use it, so the instructions below skip this step.
1. Click **Next**.
{% hint style="info" %}
#### Moving Between Stages
You can't move to the next stage while a step that is turned on has empty required fields. Complete the step's required fields or turn the step off. A green check on a stage means you have visited it, not that it has steps turned on. The **Summary** panel shows which steps are **Enabled**.
{% endhint %}
{% endstep %}
{% step %}
### Configure the Post-config Steps
The **Post-config Steps** stage holds steps that configure the sandbox, such as restoring Connected Apps, scheduled Apex jobs, and named credentials. This example doesn't use them, so the instructions below skip this stage.
1. Click **Next**.
{% endstep %}
{% step %}
### Configure the Data Migration Step
The **Data Migration** step copies records into the sandbox with a Data Migrator template.
1. Click the **Data Migration** toggle to turn on the step.
2. Click the **Template** dropdown menu.
3. Select the Data Migrator template that copies the records you want.
4. (Optional) Enter a **Root record limit** to limit the number of root object records copied into the sandbox.
5. Click **Next**.
{% endstep %}
{% step %}
### Configure the Flosum Topology Step
The **Connect to Flosum Topology** step sets the environment of the sandbox's organization in Global Settings and assigns it apps.
1. Click the **Connect to Flosum Topology** toggle to turn on the step.
2. Click the **Environment** dropdown menu.
3. Select **Dev**, **QA**, **Test**, or **Prod**.
4. Click the **Assign applications** dropdown menu.
5. Check each app to assign to the sandbox's organization.
{% hint style="warning" %}
#### Assign Only Apps a Sandbox Can Use
Check only apps that your tenant's Global Settings can assign to a sandbox. If the template assigns an app that the sandbox can't be assigned, the **Flosum topology** step fails and the sandbox is left **Incomplete**. For example, Audit & Compliance can't be assigned to a sandbox, so don't check **Audit Compliance**.
{% endhint %}
{% endstep %}
{% step %}
### Save the Template
1. Click **Save Changes**.
2. Click **Close** to return to the **Templates** page.
3. The template appears in the **Templates** list with the steps it runs.
{% hint style="info" %}
#### Templates and Topologies
A template is available only in the topology where you create it. You can use it with any source organization in that topology.
{% 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/templates/creating-a-template.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.
