Introduction
Tags classify devices so you can filter them, target them with automations, and apply monitoring policies at scale. Assign a tag and everything configured to target that tag kicks in automatically — the right automation runs, the right monitors apply.
🎬 VIDEO
How Tags Work
A tag is a label on a device. On its own, it does nothing. The power comes from what's attached to it: automations that target that tag, monitors that target that tag, filters that use that tag.
When you apply a tag to a device, every automation and monitor targeting that tag immediately applies to that device. Supprimer the tag, and they stop applying. The tags on a device reflect its current state.
This is the core pattern in Level: tags as desired state.
The Tag-Automatisation-Moniteur Loop
Here's a concrete example. You create a tag called AV. You then:
Build an automation that targets
AV— it installs your AV softwareBuild a monitor policy that targets
AV— it monitors for AV health
Nonw the workflow is: apply AV to a device, and installation and monitoring begin. Supprimer AV, and a second automation uninstalls the software and the monitor stops applying.
You don't have to touch individual devices. The tag drives the state.
💡 CONSEIL : This pattern works for any software or configuration. Créer a tag for each thing you want to manage — OFFICE, HUNTRESS, EXCHANGE, DC — then wire automations and monitors to those tags.
Tags Versus Groupes
Groupes determine structure and permissions. Tags drive policy. A device belongs to a group; it can carry as many tags as you need. Use groups to organize your fleet and control access, use tags to target automations and monitors.
Creating Tags
Tags can be created two ways: inline from the tag picker when assigning, or from the Workspace → Tags page.
From the Tag Picker (Inline)
When you open the tag picker on either the device listing or device details, a Créer new tag option appears at the bottom of the dropdown. Tapez a name and select a color to create the tag and assign it in one step.
ℹ️ REMARQUE : Tag names always display in uppercase. You can type in any case when creating, but the name will appear uppercase everywhere in Level.
From the Tags Page
Navigate to Workspace → Tags.
Cliquez sur + Créer tag in the top-right corner.
Entrer a name, add an optional description, and choose a color under Appearance.
Cliquez sur Enregistrer changes.
💡 CONSEIL : Use the description field to document what a tag does — especially on tags that drive automations or monitors. It saves future confusion when someone sees ENCRYPTED in the list and wonders what triggered it.
Assigning Tags to Appareils
Tags can be assigned from 3 places: the device listing, device details, and automations.
From the Appareil Listing
Check the box next to one or more devices.
Cliquez sur le tag icon button in the action bar (to the left of Assign to group).
Check any tags to assign. Uncheck to remove.
To create a new tag inline, click Créer new tag at the bottom of the dropdown.
This is the fastest way to tag devices in bulk.
From Appareil Détails
Open any device by clicking its name in the device listing.
On the Aperçu tab, click the tag icon button in the top-right toolbar (next to the flag icon).
Check any tags to assign. Uncheck to remove.
To create a new tag inline, click Créer new tag at the bottom of the dropdown
Once applied, tags show as colored badges near the device name.
From Automatisations
Automatisations can apply and remove tags as actions — this is how dynamic tagging works. See Dynamic Tagging with Automatisations below.
Working with Tag Badges
Cliquez suring any tag badge — on the device listing, device details, or anywhere tags appear — opens a context menu with three options:
Modifier tag — opens the tag's settings page to rename, update the description, or change color
Supprimer tag — removes the tag from that device
Afficher all tag targets — shows all devices currently carrying that tag
This is a fast path to tag management or scoped device filtering without navigating to Workspace.
Default Tags
Level includes a Default Tags automation that runs automatically and applies SERVER and WORKSTATION tags based on each device's OS — workstation OSes get WORKSTATION, server OSes get SERVER.
These defaults are a starting point, not a fixed behavior. To change which tags get applied, remove the defaults, or adjust the logic, edit the Default Tags automation in Automatisations.
ℹ️ REMARQUE : Because SERVER and WORKSTATION are applied automatically on enrollment, they're reliable anchors for any automation or monitor policy that should broadly target one device class without manual tagging.
Managing Tags
All tags live in Workspace → Tags. The tag list shows each tag's name, device count, linked policies, linked automations, creation date, and creator.
The device and automation counts are clickable — they take you directly to the filtered list of devices or automations associated with that tag.
Cliquez suring any tag name opens the tag detail view with four tabs:
Paramètres — rename, add a description, change color
Appareils — all devices currently carrying this tag
Linked automations — automations targeting this tag
Linked policies — monitor policies targeting this tag
ℹ️ REMARQUE : Tags don't affect permissions. Groupe membership controls technician access to a device. Tags are purely for classification and policy targeting.
Dynamic Tagging with Automatisations
Manually tagging every device is error-prone. A missed tag means an automation doesn't run, a monitor doesn't apply, and something slips through. The better approach: let automations handle tagging automatically.
An automation can evaluate a condition — is this device in a specific group? Is software X installed? Does a script return a particular value? — and apply or remove a tag based on the result.
Example: Managed Client Enrollment
A device is enrolled. An automation checks a custom field to determine whether the device belongs to a managed client. If it does, it applies the AV tag — which triggers a second automation to install AV software and pulls in the monitor policy to monitor AV health.
If that client later becomes unmanaged, the automation removes the AV tag. The uninstall automation fires, and the monitor policy stops applying. The whole thing unwinds automatically.
Example: Scheduled Action with Cleanup
Apply a RESTART TONIGHT tag to devices that need a reboot. An automation targeting that tag runs at midnight, reboots the device, then removes the tag. The action happens once, without you having to remember to un-tag anything.
⚠️ WARNING: If you remove a tag that's targeted by a monitor policy, that policy stops applying to the device immediately. Make sure tag removal is intentional when monitors are in play.
For full details on building tag-based automations, see Automatisations → Triggers and Automatisations → Actions.
Filtrering by Tag
From the device listing, click Filtres and select Tag to filter down to devices carrying a specific tag. You can combine tag filters with other criteria like group, OS, or online status.
Cliquez suring Afficher all tag targets from any tag's context menu does the same thing — it jumps you straight to a filtered view of that tag's devices without manually setting up the filter.
Questions fréquemment posées
Who can create and assign tags? Any technician with access to the device can assign existing tags from the device listing or device details. Creating new tags and managing tags globally requires access to Workspace → Tags. If you can't see the Workspace section or the tag assignment option, check your permissions with your Level admin — see Workspace → Autorisations.
What's the difference between tags and groups? Groupes define your fleet's structure and control which technicians can access which devices. Tags drive automations and monitoring policies. A device is in one group; it can carry as many tags as needed.
Can a device have multiple tags? Oui, there's no limit. A device can carry tags for its role, installed software, monitoring tier, or anything else you want to track.
Why isn't my automation running after I apply a tag? Check that the automation's trigger is configured to fire on that specific tag and that the automation is assigned to the correct group. If the automation still isn't running, see Automatisations → Questions fréquemment posées for troubleshooting steps.
What happens if I delete a tag that's still assigned to devices? Deleting a tag removes it from all devices and from any automations or monitor policies targeting it. Those policies stop applying immediately. Review a tag's linked automations and policies in Workspace → Tags before deleting.
Can I rename a tag without breaking automations and monitors? Oui. Renaming a tag updates it everywhere — devices, automations, and monitor policies all reference the same tag object. The rename propagates automatically.
Can I search for a tag in the picker? Oui. There's a search field at the top of the tag picker dropdown. Tags can't currently be sorted, so search is the fastest way to find a specific tag in a long list.