Enabling Field History Tracking is two settings deep but the field-selection decision needs business and compliance input. The steps below cover both halves.
- Gather compliance requirements
Identify which fields require audit logging based on regulatory frameworks (SOX, HIPAA, internal controls). Get the list signed off in writing.
- Open Set History Tracking
Object Manager > Object > Fields and Relationships > Set History Tracking. The page lists all fields with a checkbox each.
- Enable object-level tracking
Check Enable History Tracking at the top of the page. Without this, no field tracking takes effect even if individual fields are checked.
- Check the target fields
Check the fields gathered from compliance. Stay within the 20-field cap; if more are needed, evaluate Field Audit Trail.
- Save and confirm
Save the settings. Edit a test record's tracked field and confirm a History record is created (query AccountHistory or check the History related list on the record).
- Add the History related list to layouts
Page Layout Editor > drag the History related list onto the record layout. This gives end users visibility into recent changes without needing reports.
- Build reports
Use the standard report type for the History object, or build a custom report type joining History to the parent. Schedule weekly for audit and compliance teams.
Master toggle per object. Required for any field tracking to take effect.
Individual fields to track. Up to 20 per object under standard licensing.
Extends retention to 10 years and field cap to 60. Licensed separately.
Page layout component showing recent History records on the record page. Adds the audit log to the end-user UI.
Built on History objects for richer reporting. Standard report types are limited; custom types unlock joining with parent.
- Tracking is not retroactive. Activation logs only future changes; prior history is not recoverable. Activate early for compliance objects.
- The 20-field cap is per object. Hitting the cap on a key object usually requires either Field Audit Trail or a tough prioritization conversation with compliance.
- Long text, formula, and some encrypted fields cannot be tracked. Confirm trackability against the field type list before promising coverage.
- Default retention is 18 months. Records older are auto-deleted with no recovery. For multi-year audit, Field Audit Trail is the only path.
- Bulk updates produce one History record per changed record. A bulk load updating 10,000 records on a tracked field writes 10,000 History rows, which can spike storage and reporting cost.