Plan requirement
| Subscription | Any plan |
| Access | Admin |
Retention for the records you defined yourself. Easy to forget, because they were built for a purpose that may have ended.
Create one
- Open Admin Center, then Account, then Security, then Deletion schedules.
- Choose the custom object.
- Set the age at which records are removed.
- Check what depends on those records first.
Check the dependencies first
Custom object records are usually referenced from tickets: an asset, a contract, a device. Deleting the record can leave those references pointing at nothing.
Look at what links to the object before setting any period.
They hold personal data too
An object holding customers' devices, addresses or contract details is personal data, and it falls under the same obligations as anything else. It is also the part most often left out of a retention review, because it was built by somebody solving a specific problem.
Retention is not one number
An asset record probably outlives the tickets about it. A temporary registration for an event does not. Each object deserves its own period rather than inheriting the ticket one.
Objects that stopped being used
Almost every account has one built for a project that ended. Those records serve nothing and are still your responsibility, and this is a good moment to notice them.
Test on a small object first
Run it on something low-stakes to see the effect, then apply it more widely. The mechanism is the same and the confidence transfers.
Comments
0 comments
Article is closed for comments.