Plan requirement
| Subscription | Suite Enterprise or higher, Support Enterprise |
| Access | Admin |
A recorded state of your configuration. What you compare against when something behaves oddly, and what you go back to.
Take one
- Open Admin Center, then Account, then Sandbox, then Snapshots.
- Create a snapshot.
- Name it for the moment it captures.
- Take another before any significant change.
Name it for the moment
"Before SLA rework, 12 March" tells you what it is. "Snapshot 4" means that when you need it, you will be guessing between three of them.
Take one before every substantial change
It costs a minute and it is the difference between "put it back" and "work out what it used to be". The moment you most want one is exactly the moment you cannot create one retrospectively.
They answer what changed
Something behaves differently and nobody remembers touching it. Comparing today against a snapshot from before answers that in minutes rather than by reading every trigger.
Not a backup of your data
Configuration only. Your tickets, customers and comments are not in it, and it does not substitute for a data export.
Keep a few, not many
The last known-good state, and one before each significant piece of work. A long list of unnamed snapshots is as unhelpful as none.
Note why you took it
One line, wherever your team keeps such things. The snapshot records what the configuration was; only you can record what you were about to do to it.
Comments
0 comments
Article is closed for comments.