Template

A Template contains the full definition of a Sandbox and is used to quickly replicate sandboxes from that definition. Templates help teams maintain well-crafted, standardized environments that can be rapidly replicated for individual developers.

When an org admin has set up a sandbox with the right workloads, tools, configurations, and automation, they can save that definition as a template. Developers can then create their own sandbox from the template with a single click, getting a fully configured environment ready for work almost immediately.

Relationship to Sandboxes

When a sandbox is created from a template, the template's definition is cloned into the sandbox. This means that subsequent changes to the template do not automatically propagate to existing sandboxes. To synchronize an existing sandbox with an updated template, the Sandbox Resync operation must be performed explicitly.

Sandbox Pool

A Sandbox Pool can be associated with a template to maintain a number of pre-warmed, ready-to-use sandboxes. When a developer creates a new sandbox from that template, a pre-warmed sandbox is picked from the pool and handed off immediately, skipping the setup time entirely.

See Also

• Sandbox — the fundamental unit defined by a template
• Sandbox Pool — pre-warming sandboxes for instant availability
• Sandbox Resync — syncing a sandbox back to its template
• Workspace Snapshots — snapshots referenced in templates
• Dependency Snapshot — pre-seeding dependency data via templates