Hello everyone,
When multiple departments operate within the same system, parallel testing often becomes essential. Each team may be working on separate configurations, workflows, or automation rules at the same time.
Without a way to isolate these configurations, changes made by one team could inadvertently impact the other development processes, leading to confusion and inefficiencies.
Until now, having a single sandbox account has enabled teams to test individual configurations and validate them thoroughly before deploying to production. This meant every department had to run their tests individually to avoid cross-departmental interference.
Now, with the introduction of multiple sandbox accounts, administrators can create up to three distinct sandboxes, enabling teams to test and deploy configurations in isolation. This enhancement empowers departments to assess their specific workflows independently, ensuring that configuration are validated without risk of conflicting changes.

What’s new and improved:
- Independent sandbox accounts: Each department can create its own sandbox to test configurations. For example, the customer support team can validate automation changes without affecting the delivery team's layout updates.
- Sequential processing of operations: Build, rebuild, and deployment operations are processed sequentially across sandboxes to ensure orderly configuration management.
- Controlled deployment: Only one sandbox can deploy changes to production at a time, providing a controlled and reliable deployment process.
Availability
- Editions: Enterprise edition
- DCs: All DCs
PM: @Nivedhan Senthilkumar
Regards,
Velantina | Zoho Desk - User Education