User Guide

How to Enable Change Tracking

This guide shows you how to turn on Change Tracking for a site, choose a retention period, and select which attributes to track.

Prerequisites

  • Administrator role on the target site.
  • An understanding of which attribute categories your site needs to track. See the Change Tracking Reference for the full list.

Steps

  1. Open Admin Center > Site Settings > Settings > Change tracking.

  2. Switch the Change tracking enabled toggle to ON.

  3. Choose a Retention period from the combobox. Available values are 6 months, 1 year, 2 years, 3 years, 4 years, and 5 years.

    Important: The retention period applies going forward. Records older than the new value are still purged when their original retention elapses.

  4. Expand each Tracking category card and review its sub-attribute checkboxes. Tick the optional sub-attributes you want to track; required sub-attributes are already selected and cannot be cleared:

    • General — disk drives, software groups, memory, monitors, network adapters, printers, video adapters.
    • System — asset tag, computer name, DNS name, domain, OS name, MAC address, IP address, serial number, total space.
    • Security — antivirus level, antispyware level, auto-update level, Windows firewall level, internet settings level, service level, UAC level.
    • User accounts — description, domain, enabled, last logon, name.
    • AWS assets — resource name.
    • Azure assets — resource name.
    • Custom audit fields — your site's custom fields.
  5. Save the settings.

Note: Change events are recorded for selected sub-attributes. If a category has no selected sub-attributes, it produces no change history.

Verify

  1. Wait for the next audit cycle to produce a snapshot for at least one device.
  2. Open the device form from Inventory and switch to the Change history tab.
  3. Confirm that change events appear with Date, Type, Category, Attribute, Old value, and New value columns populated.
  4. Open Admin Center > Site Settings > Logs > Change log and confirm that configuration-level events (such as the change-tracking edit you just performed) are recorded.