Introduction
You don't have to build automations from scratch. Every new Level account comes with a Get Started automation group pre-populated with common automations — Windows Patching, macOS Patching, Linux Patching, Default Tags, Disk Cleanup, and more. They're fully functional as-is. Enable what you need, adjust what doesn't fit, and use the rest as a reference when you build your own.
The Get Started Group
Navigate to Automations in the left sidebar. You'll see a Get Started group in the left panel. Click it to see the automations included.
The Status column shows each automation's current state:
Manual — The automation exists but won't run until you trigger it manually or change the status.
Active — The automation is live and will fire automatically based on its trigger.
Most Get Started automations ship as Manual so they don't run until you've reviewed them. This is intentional — take a few minutes to check each one before enabling.
What's Included
Here's a summary of the automations in the Get Started group:
Default Tags Runs when a new device is detected. Automatically applies device-type tags (Workstation and Server) based on what the device reports. This one is enabled by default — it's usually the foundation everything else builds on.
Windows Patching Schedules Windows Update runs on enrolled Windows devices. Review the trigger, schedule, and any conditions before enabling to confirm the timing fits your maintenance windows.
macOS Patching Same as Windows Patching, for macOS devices.
Linux Patching Same for Linux.
Disk Cleanup Runs disk cleanup tasks on devices to recover space. This can be connected to a disk monitor to run automatically when space is low.
Prompt User to Restart Prompts end users to restart when a device has been running too long. Useful for enforcing restart hygiene without forcing a reboot.
Lost / Stolen Endpoint A response automation for when a device is reported lost or stolen. Review and enable the Tag Applied triggers, so you can tag a device as Lost or Stolen to have this automation run automatically.
Install Microsoft 365 Installs Microsoft 365 on a device. Review the action to confirm it's installing the right edition for your environment.
Enabling an Automation
When you're ready to turn an automation on:
In the Get Started group, click the automation you want to enable.
Review the trigger, actions, and any conditions. Make adjustments if needed (see below).
Enable or toggle the trigger in the automation.
ℹ️ NOTE: Automations with a Schedule trigger start running at their next scheduled time after you enable them. Automations with event-based triggers (like New Device Detected) fire the next time the trigger condition is met.
Common Adjustments
Patching automations
The patching automations run on a schedule and use a platform condition to target devices — Windows Patching runs on all Windows devices, macOS Patching on all macOS devices, Linux Patching on all Linux devices.
Confirm the conditions for the scheduled trigger.
Check the schedule. The default timing may not align with your maintenance windows.
Decide whether you want devices to prompt for a restart or restart automatically after updates.
Default Tags automation
Open it and review the tags it applies.
Building from the templates
These automations also serve as working examples. When you're ready to build your own, open one, duplicate it, and modify the copy. It's faster than starting from a blank automation.
💡 TIP: For a detailed walkthrough of how automations work — triggers, actions, conditions, and assignment — see Automations Overview.
Patching Without Automation
If you want to push updates to a device without setting up an automation, you can do it manually from the Updates tab in the device detail view, or from the global Updates view. See Updates for details.
FAQ
Why are all the automations set to Manual by default? So they don't run before you've reviewed them. Level doesn't know your maintenance windows, your tag conventions, or your environment — the automations are set up to be correct, but you should confirm they match your setup before enabling.
Can I move these automations out of the Get Started group? Yes. You can reassign automations to any group or leave them in Get Started — the group is just organizational. It doesn't affect how the automations run.
What happens if I enable a patching automation right away? The patching automations target by platform, not by tag, so they'll run on any enrolled device of that OS type. If you're not ready for that yet, leave the triggers disabled until your maintenance windows are confirmed and your device inventory is in order.
Can I delete automations from the Get Started group? Yes. If an automation doesn't apply to your environment, delete it or archive it. The Get Started group is a starting point, not a requirement.
Where do I go to build my own automations from scratch? See Automations Overview for a full guide, or click + Create automation in the Automations page.