Plan requirement
| Subscription | Suite Growth or higher, Support Professional or higher |
| Access | Admin |
Making one, and the three things to do immediately afterwards so it stays useful and cannot email your customers.
Create it
- Open the sandbox settings in Admin Center.
- Create a sandbox and choose what it copies.
- Wait for it to be built.
- Sign in and check your configuration arrived.
One: check the email
The most important step. A sandbox with working outbound email can send real messages to real addresses, from a system where you are deliberately testing badly configured triggers.
Confirm what it can send before building anything that notifies anybody.
Two: add the people who will use it
Sandbox accounts are separate. Whoever tests there needs an account there, and that is easier to arrange now than in the middle of a change.
Three: name it unmistakably
The interfaces look identical, and admins do end up making changes in the wrong one. Anything you can set to make it visually distinct is worth doing.
What it copies
Configuration: triggers, automations, fields, forms, views, macros. Not your tickets, and not your customers, though what exactly comes across depends on your plan.
Check what arrived rather than assuming.
Refresh before serious work
It stops matching production the moment either changes. Testing in a stale sandbox produces confidence that does not transfer.
Comments
0 comments
Article is closed for comments.