Last updated: 2025-03-25
Source: https://support.freshservice.com/support/solutions/articles/50000009707-sandbox-overview
When your service desk offers multiple capabilities that are often subject to change, managing and testing before changes are deployed to production could become challenging. The new Sandbox helps you set up copies of your production to manage changes with evolving business needs without impacting users.
Here is an overview of how the process with Sandbox works.
How is the new Sandbox different from the outgoing version?
| Outgoing Sandbox | New Sandbox |
| Destroys on sync or in 180 days, whichever is earlier. | Exists perpetually unless deleted. |
| Syncs all data at once. | Users can selectively choose a set of configurations to sync. |
| A sandbox needs to be created for every workspace. | Sandbox creation copies all the workspaces from the Production. |
| Sync is one-way (Sandbox to Production). | Sync is bi-directional (Sandbox to Production or Production to Sandbox). |
The new Sandbox allows you to play around with a near-live instance without risk of disruption or downtime. With the new Sandbox you can
What is a Sandbox? Why should you use it?
Sandbox is a copy of your production environment that offers a risk-free environment to:
Where can you find Sandbox in Freshservice?
The Sandbox module can be found in Admin -> Account Settings -> Sandbox. Learn who can view the Sandbox module.

The Sandbox home page consists of three tabs:
1) 'Sandbox' that shows basic Sandbox information, such as name and description. It also allows you to visit, view, or delete an instance.
2) ' Outward Sync' helps you keep track of all the syncs initiated from an instance to any other instances. For example, the Outward sync tab in Sandbox lists the syncs initiated to target instances such as Production.
3) ' Inward Sync' helps you keep track of all the syncs that are coming into the instance, an inverse of Outward Sync.
