Custom Fields
Model your own device attributes.
Custom Fields extends endpoint records with metadata specific to your operating model.
Why It Exists
Standard inventory fields do not capture every business context needed for service delivery. Teams often need attributes like owner, support tier, cost center, criticality, or contract scope.
Operational Uses
Custom field values can drive:
- search and filtering
- targeting for policies and deployments
- report segmentation
- technician context during incident workflows
Data Quality and Scope
Custom field definitions are tenant-aware and validated so organizations can model their own data without weakening consistency.
Practical Rollout Approach
Start with a minimal, high-value schema and only add fields that support a concrete decision or workflow. This keeps metadata useful and maintainable.
Why It Matters
Custom Fields makes Breeze adaptable to real service operations without forcing brittle workarounds in naming conventions or external spreadsheets.
Capabilities
Flexible Attribute Schema
Define field names and types to capture owner, tier, cost center, or any business-relevant device attribute.
Operational Targeting
Custom field values drive search, policy assignment, deployment scope, and report segmentation.
Validated and Tenant-Scoped
Field definitions are validated and isolated per organization to maintain data consistency across teams.
Incident Context Layer
Fields surface in device views during triage, giving technicians relevant business context without external lookups.