Administration Guide

Change Tracking Reference (admin)

Reference for the per-Site Change tracking configuration: toggle, retention, categories, sub-attributes, and the places where change events appear.

Admin Center > Site Settings > Settings > Change tracking.

Configuration fields

Field Type Default Description
Enabled Toggle OFF Master switch. While off, no Change Events are ingested; existing change history is retained until retention expiry or manual purge.
Retention period Combobox 2 years One of 6 months, 1 year, 2 years, 3 years, 4 years, 5 years. Records older than this are auto-purged on a rolling basis.
Tracking categories Multi-select with sub-attribute checkboxes - Seven categories - see below. Each category has sub-attribute checkboxes for fine-grained selection.
Purge change history Button - Manually clears all stored change history. Destructive. See How to purge change history.

Tracking categories

Seven categories are exposed in the UI:

Category Typical sub-attributes Notes
General Name, location, owner, department Device-record metadata.
System OS version, BIOS, hardware components Audit-driven.
Security User accounts, group membership, security settings Subset of audit data.
User accounts Local users, password age, last logon OS-specific.
AWS assets EC2 instance state, IAM, tags Cloud audits required.
Azure assets VM state, subscription, RBAC Cloud audits required.
Custom audit fields Per-field deltas Driven by Custom Audit Fields Reference - once a field is defined, its values are tracked here too.

Software-change scope (RFC C023901)

For software changes, you can choose which software groups to track: Required, Forbidden, or Regular. This lets Change Tracking record only the software installs and removals you want to monitor.

Where change events appear

Location Scope Source
Per-device Change history tab One device Audit-driven changes for that device.
Site-wide Change log One Site Both audit-driven device changes and config-level changes (Sites, Users, Segments, Reports, Tags, Notification templates) with Added / Modified / Deleted verbs.

State machine

Toggle state New events ingested Existing history
Enabled = ON yes retained until retention expiry or manual purge
Enabled = OFF no retained until retention expiry or manual purge

Turning Enabled off does not delete existing records; it only stops new ones from being created.

Constraints

  • Change tracking is per-Site. There is no cross-Site change-history view.
  • Pre-existing changes (those that occurred before Enabled was switched on) are not retroactively created.
  • Each category contains its own list of sub-attribute checkboxes. Optional sub-attributes can be selected or cleared; required sub-attributes are selected by default and cannot be cleared.
  • For software changes, tracking can be limited to selected software groups: Required, Forbidden, or Regular.

RBAC

Action Site Administrator Site User
Toggle Enabled yes no
Set Retention period yes no
Pick categories and sub-attributes yes no
Click Purge change history yes no
View per-device Change history yes yes
View site-wide Change log yes no