Introduction
Install pending updates on managed Linux devices via automation. Use this action to keep Linux systems current, apply security patches on a schedule, or enforce update compliance as part of a broader device management workflow.
Install Linux Updates
From the automation pipeline in edit mode, click + Add action and select Install Linux updates from the Security category. The action panel opens with two sections: Action type (pre-set to Install Linux updates) and Step configuration.
Configure Update Categories
Click Configure update categories to open the Linux patch management categories panel. Check the categories you want Level to install. Unlike Windows and macOS, Linux categories don't have timing delays — Level installs updates in the selected categories immediately each time the action runs.
💡 TIP: At minimum, enable Security updates on all Linux devices. Kernel updates are important but can require a reboot — pair with Reboot after updates and schedule this automation during a maintenance window.
The available categories are:
Category | Description |
Kernel updates | Updates to the Linux kernel |
Security updates | Product-specific, security-related vulnerability fixes |
General updates | Non-security critical bug fixes covering compatibility, performance, and interoperability improvements |
ℹ️ NOTE: Linux update categories don't support delay installation. If you need to stage Linux updates before broad rollout, use a canary group — tag a small set of test devices, run this action against that group first, and roll out to the wider inventory once you've confirmed no issues.
Reboot After Updates (When Required)
When enabled, Level reboots the device after updates install — but only when a reboot is required to complete installation. Updates that don't need a reboot won't trigger one.
⚠️ WARNING: This reboot happens without prompting the end user. Use this in combination with a maintenance window, or pair with the Notify User action beforehand if users may be active on the device.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action. Expand the section to add conditions.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for execution settings including action name, failure behavior, output variables, and retries.
See Actions Overview for the full reference on additional options available on every action.
FAQ
Does this action work on Windows or macOS? No. This action applies to Linux devices only. For Windows, use the Install Windows Updates action. For macOS, use the Install macOS Updates action.
Why are there no timing delay options for Linux? Linux update categories are enable/disable only — there's no per-category delay like Windows and macOS offer. If you need to stage rollouts before broad deployment, use a tagged canary group with a separate automation instance to validate updates first.
Do updates install silently? Yes. Updates install in the background via the system package manager. End users don't see prompts. If a reboot is required and Reboot after updates is enabled, the device reboots without a user prompt.
What happens if there are no pending updates in a selected category? Level skips that category silently and continues. The action completes successfully even if nothing was installed.
What happens if the device is offline when the action runs? The action queues and resumes once the device comes back online.
Who can add or modify this action in an automation? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.