Custom Audit Fields Reference
Custom audit fields are per-site, user-defined fields scoped to a specific device type. They extend the audit data model with values collected during audit through a PowerShell script or an SNMP OID, and surface alongside the built-in fields in Inventory grids, reports, and change tracking.
Where they live
Admin Center > Site Settings > Customization > Custom audit fields. The grid groups records by Device type and exposes columns such as Name, Label, Field type, Device subtype, Description, and Script.
Fields
| Field | Type | Values | Default | Description |
|---|---|---|---|---|
| Name | string | Identifier characters | none | Internal identifier used in API and scripts. |
| Label | string | Free text | none | Display text shown in Inventory grids and on the device form. |
| Description | text | Free text | empty | Free-text description of the field's purpose. |
| Device type | enum | Windows computer / SNMP device / AWS resource types / Azure resource types | none | Required. Determines which device or resource records carry this field. |
| Device subtype | enum | Printer / Switch (SNMP only) | none | Required for SNMP device fields; constrains the field to a specific SNMP subtype. |
| Field type | enum | Depends on the device type | none | Data type of the collected value. SNMP supports Memo and String; Windows supports a broader set including Table and Logical. |
| Script | text | PowerShell script | none | Required for Windows computers and AWS or Azure resources. |
| SNMP OID | text | OID | none | Required for SNMP device fields. Enter the OID directly, or use Use MIB Browser to select it from a MIB file. |
Collection input by device type
Custom audit field setup depends on the selected Device type.
For Windows computers and AWS or Azure resources, the form includes a Script editor. Enter or load a PowerShell script that runs during audit and returns a value matching the selected Field type.
For SNMP devices, the form includes Device subtype and SNMP OID fields. Enter the OID directly, or turn on Use MIB Browser to upload or select a MIB file and choose the OID through the browser.
Constraints
- Custom audit fields are scoped to a single Device type and, for SNMP device fields, to a Device subtype. A field defined for Windows computers does not appear on macOS, Linux, AWS, Azure, or SNMP devices.
- Values are populated on the next audit after the field is created. Existing snapshots are not retroactively re-audited.
- Custom audit fields integrate with Change tracking: the Custom audit fields category on Admin Center > Site Settings > Settings > Change tracking lists each field as a sub-attribute that can be ticked to track value changes.
- Custom audit fields appear as columns in Inventory grids, as filter / Group By targets in saved views, and as columns in Reports exports.
- Only Administrators create, edit, or delete custom audit fields.
- To show related custom fields as a single column in a combined Inventory view, create separate fields for each device type and use the same Label.
Per-device-type type matrix
| Device type | Field type options | Collection input |
|---|---|---|
| Windows computer | Currency / Date / DateTime / Integer / Logical / Memo / String / Table | PowerShell script |
| SNMP device (Printer / Switch) | Memo / String | SNMP OID; optional MIB Browser |
| AWS and Azure resources | Device-type-specific field types | PowerShell script |
States
A custom audit field has the following implicit states:
- Defined, not yet collected - the field exists; no device snapshot has provided a value yet.
- Populated - at least one device has a value collected through the configured input.
- Stale - the value persists from a previous audit; if the next audit cannot collect a fresh value, the previous value is retained rather than blanked.
Related
- Device form Reference - where collected values appear on the device
- How to create a custom view - show or filter custom field columns
- PowerShell Examples for Custom Audit Fields - sample scripts for Windows custom fields
- About Inventory - how custom fields fit alongside built-in audit data