Administration Guide

Custom Audit Fields Reference

Reference for the per-Site, per-device-type Custom audit field catalog: list view, fields on the create form, surfaces, and constraints.

Admin Center > Site Settings > Customization > Custom audit fields.

List view

Records are grouped by Device type. Within each group:

Column Type Description
Name String Internal identifier (column key). Sorted ascending by default.
Label String Display label used on the device form and inventory grid.
Field type Enum Data type for the collected value.
Device subtype String For SNMP devices: Printer or Switch. Empty for other device types.
Description String Optional human-readable description.
Script String PowerShell script body for Windows computers and AWS or Azure resources.

Toolbar: Default View / + New field / Delete / Filter / More actions / Grid settings.

Fields on the create form

Field Required Description
Label yes Display label shown in inventory grids and the device form.
Name yes Internal identifier. Becomes the column key in inventory grids.
Device type yes One of Windows computer, SNMP device, AWS resource types, Azure resource types, and others. The field only applies to devices or resources of this type.
Device subtype yes, for SNMP device fields For SNMP, narrows the field to Printer or Switch.
Field type yes Data type for the collected value.
Script yes, for Windows computers and AWS or Azure resources PowerShell script that collects the value during audit.
SNMP OID yes, for SNMP device fields OID used to collect the value. Enter it directly, or turn on Use MIB Browser to select it from a MIB file.

Note: Optional fields on the create form depend on the selected Device type.

Where custom fields surface

Surface Behavior
Device form Visible on the device's form for any device of the matching type.
Inventory grid Available as an optional column with filter support.
Change tracking Captured under the Custom audit fields tracking category when Change tracking is enabled.

Cloud-resource scope

Custom audit fields apply to AWS and Azure cloud-resource audits as well. When Device type is an AWS or Azure resource type, the field populates on those audited objects through the corresponding cloud audit path.

Constraints

  • A custom field is per-Site. There is no instance-wide custom-field catalog.
  • A custom field is bound to a single Device type. Apply to multiple types by creating one field per type.
  • Custom fields populate on subsequent audits, not retroactively. Re-audit affected devices to back-fill.
  • The supported Field type values and collection input depend on the selected Device type.

RBAC

Action Site Administrator Site User
Open the catalog yes no
Create a custom field yes no
Delete a custom field yes no