Tags
Lightweight fleet segmentation without rigid structures.
Tags are a fast, flexible segmentation model for endpoint operations.
Why Tags Work
Not every environment needs heavy hierarchy for every workflow. Tags let teams quickly classify devices by environment, function, customer label, compliance scope, or rollout cohort.
Operational Uses
Tags are especially useful for:
- search and filtering
- policy targeting
- deployment scoping
- temporary incident cohorts
Governance Notes
Because tags are lightweight, consistency matters. Teams benefit from simple naming standards so targeting and reporting remain predictable.
Where They Fit
Use tags for adaptable segmentation and combine them with groups and policies when you need more formal structure.
Best Practices
Treat tags as operational labels, not free-form notes. A small naming standard (for example: env:prod, role:sql, sla:gold) prevents drift and makes targeting safer over time.
Review high-impact tags periodically to remove stale values that can accidentally expand deployment or policy scope.
Capabilities
Array-Based Tag Model
Tags attach as arrays on device records for low-overhead segmentation without rigid hierarchy.
Multi-Workflow Targeting
Tag values drive search, filtering, policy scope, deployment targeting, and temporary cohort assignments.
Naming Standard Governance
Consistent tag naming (e.g., env:prod, role:sql) prevents targeting drift and keeps reporting predictable.
Combined Segmentation Strategy
Use tags for adaptable segmentation alongside groups and policies for more formal operational structure.