> 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/getting-started/sandbox-management-overview.md). # Sandbox Management - Overview Sandbox Management lets you create, refresh, and delete Salesforce sandboxes from Flosum, and set up each sandbox automatically with a template after it is created or refreshed. Salesforce carries out each create, refresh, and delete with its standard sandbox process, so your sandboxes use your Salesforce sandbox licenses and appear in Salesforce Setup as usual. Every new sandbox is connected to your tenant as an organization in Global Settings, ready for your other Flosum Cloud Apps. Sandbox Management provides the following features: * **Sandboxes**: Create Developer, Developer Pro, Partial, and Full sandboxes from a source organization, and follow each sandbox's status, details, and activity from a single list. * **Templates**: Build a reusable sequence of steps that runs after a sandbox is created or refreshed, such as backing up metadata, restoring Connected Apps and scheduled Apex jobs, and copying records with a Data Migrator template. * **Flosum Topology**: Connect each new sandbox to your tenant as an organization, set its environment, and assign it apps, so it is ready to use in DevOps, Backup & Archive, Data Migrator, and Audit & Compliance. * **Refresh and Delete**: Refresh a sandbox from its source organization, or delete it when you no longer need it. ### Jump right in


Creating a Sandbox	Create a sandbox from a source organization and connect it to your tenant.	Creating a Sandbox
Creating a Template	Build a template of steps that runs after a sandbox is created or refreshed.	Creating a Template
Creating a Sandbox with a Template	Create a sandbox and set it up automatically with your template.	Creating a Sandbox with a Template

--- # 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/getting-started/sandbox-management-overview.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.