Level roadmap
Follow progress from planned work through completion. Timing may change as we learn, but the direction stays transparent.
Planned
Display Multiple Screens
When in Remote Control, Level User can choose to see all displays side by side, as well as individual displays
On/Off Toggle (Monitor Policies)
It would be nice to be able to toggle monitors on and off. The use case would be mainly for monitor development. If I have 6 monitors in one policy, being able to toggle off one particularly noisy one to fine-tune, without disabling the entire policy would be helpful.
Device Column - Serial number and MAC
Please add the ability to search devices by serial number or MAC address. They are commonly used as identifiers in systems/inventory and would help techs quickly locate a device.
Device Column - OS/Version
Please add a column option for the OS/Version under devices.
Device Column - Chassis Type / Form Factor
We have different rates for computer management based on laptop vs desktop, as we found we have to put more effort into maintaining laptops as they're most often in a backpack after-hours. It's also helpful information for our techs to know if a computer is a desktop vs. laptop as part of their support duties. Would like to request either adding a Chassis Type (or Form Factor) field in the GUI and API, or enhancing the existing Type field so that a Workstation is distinguished between a desktop and a laptop. Possibly the following WMI class would get the necessary information from the machine, for Windows. https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-systemenclosure
Device Column - User display name, upn, and email
RiIn the Device → Access information panel, the Last logged in user currently shows only the DOMAIN\samAccountName. When I’m triaging tickets, I have to take extra steps to figure out who that actually is (look up the account in AD, remote in, etc.). That slows down investigations across multiple offices. Request Please enhance this field to include a friendly identifier alongside the SAM account: Keep the existing DOMAIN\samAccountName Also show Display Name and, if available, UPN / email Example rendering: John Doe (COMPANY\john.doe) • john.doe@domain.com Nice to have Make the value clickable to filter devices by that user or open the user profile. Why it helps This removes several lookup steps per incident, speeds up response time, and reduces context switching for our technicians.
Device Column - Disk's % Free
In this example, could you add the percent free at the end? 766.20 GB free of 930.65 (82%)
Up next
Drag-and-Drop File Transfer in Remote Control
Allow technicians to drag files from their local computer directly into a browser-based remote control session. Files should automatically upload to the remote user’s desktop, eliminating the need to open the file explorer and manually navigate to an upload destination.
Notification System
Provide a centralized place for users to see what needs their attention, what’s waiting for approval, and what happened recently across their workspace. Notifications should connect users directly to the relevant task, alert, device, or activity so they can quickly review and respond.
Alert Detail View
Create a detailed view showing an alert’s history, including when it opened, closed, and reoccurred. It should also display investigations, findings, recommended solutions, actions taken, and links to the underlying script or automation runs.
Automation, Script, and Monitor Draft and Versioning
Allow users to safely propose changes to scripts, automations, and monitoring policies without immediately affecting production. Users should be able to review, publish, and restore previous versions while maintaining a clear history of what changed.
Debug Mode / Break Points
Explore a debug mode for automations that allows technicians to step through actions, set breakpoints, retry failed steps, move forward or backward, inspect errors, and modify scripts before continuing.
Sandbox and Test VMs
Provide isolated devices where users can safely build, run, and validate scripts or automations before deploying them to production. Companies could use Level-provided virtual machines or designate their own Windows, macOS, and Linux devices for testing.
Safety and Approval Controls
Give organizations control over when users can take action and when human approval is required. Controls could include requiring testing, restricting production devices, protecting sensitive systems, setting device-count thresholds, and supporting single or dual approval for higher-risk actions.
Mission Control
A centralized view of all work across the workspace. Users should be able to see what needs their attention, what happened recently, what is currently running, what is scheduled, and what is waiting for approval.
In progress
File Explorer 2.0
Create folders Rename folders/files Delete folders/files Download multiple files or perhaps folders Move/copy files Show sizes of folders so that techs can easily find offending large files/folders. Have a visual representation of the disk used space/free space Show contents and allow editing of text-based file types.
iOS / Android App for accessing Level (not Android/IOS agent)
Put the power of device management and automations right in your pocket. With this mobile-friendly solution, techs can monitor devices, troubleshoot issues, and trigger automations anytime, anywhere—keeping them connected and in control, no matter where the job takes them.
Automation Refactor
Exciting changes and improvements coming to Automations.
🔒 Stealth Initiative
This represents a larger strategic investment that we're keeping private until it's ready. We don't want to overpromise, but we're looking forward to unveiling it soon.
Completed
Bulk Import Scripts
We have hundreds of scripts to migrate, and creating them manually would be very time-consuming.
Custom Commands / Hotkeys in Remote Control Session
It would be very useful if the Remote Control viewer supported configurable custom commands or hotkeys (for example in the Commands dropdown or via predefined key mappings). System shortcuts like Win or Ctrl+Esc are captured by the local OS/browser and cannot be sent to the remote device.
Public API - Automations
It would be extremely helpful to have API support for managing scripts, automations, and their folders in Level. Today, scripts and automations must be created, updated, and organized manually through the UI. For teams with larger environments, shared script libraries, or CI/CD workflows, this makes it difficult to keep things consistent and in sync. API access would allow us to automatically deploy scripts and automations from source control (like GitHub), keep them updated over time, and organize them into standard folder structures. This would also make onboarding new users much easier by allowing teams to programmatically set up sane defaults for scripts, automations, and organization from day one. Overall, this would significantly improve scalability, consistency, and automation for advanced users and MSPs.
Run automation on another device
Build workflows that coordinate work across multiple devices.
Level CLI
Bring Level to your terminal. The Level CLI lets you manage devices, run scripts and automations, query data, and perform common RMM tasks directly from the command line.
Provide parameters to Automation/Script when invoked
It would be nice to be able to prompt the technician for parameters on some automations. For example, imagine a generic automation to create a new user. When the automation runs it could prompt for the username/password.
Per-device consent policy for remote access
Consent prompts are currently all-or-nothing at the tenant level. We need it scoped per device or device group — require end-user consent before remote sessions on standard user endpoints, but bypass consent for unattended devices like digital signage and conference room systems, which have no one present to approve the prompt. Today we either weaken consent for every device or lose remote access to unattended hardware.
Hudu Integration - Archive Endpoints
On the Webinar with Hudu today, a customer pointed out that we should be archiving Hudu endpoints when they are deleted from Level.
Absolutely Disallow Technician Access
Since Level doesn't have the ability to dish out permissions to end users and/or business owners that want access to devices we need to add a user "tech" and assign specific permissions. When speaking to a business owner they asked why they had servers in there view that they didn't know about. Come to find out they have access to the root of the organization and whatever device group they are assigned. I'd like to see the ability to not allow that and define only specific folder access including the root device group directory.
Remote control scaling
Allow screen scaling when viewing on a large or small display.
Device Column - Custom fields
The ability to add custom fields to the device listing.
Application Management
There's a lot here, so this will certainly take time, but we want to be thinking big picture. Please add/discuss ideas! Global Application View - that would show all applications installed (including version, date installed, etc) Ability to install/uninstall applications Have the ability to create a list of trusted applications, or perhaps denied applications. (probably need both) Alerting (or better yet, enforcement) when an unauthorized app is installed, or if a mandatory app is missing. (See CIS control #2) Application Search/Filters on the device page Show application versions. Ideally this is tied into repos for updating (Winget, Brew, APT) so that we can compare to the latest release. Pin an application to a specific version so that patch policies will not update it.
Remote Execution - Automation Action
New Automation Action that allows you to run an action on another device, instead of the device flowing through the automation.
Store BitLocker recovery keys.
Level should pull the BitLocker recovery keys from windows Server\Workstations and display it in the portal.
Command palette
Quickly navigate Level and take action from anywhere. The Command Palette gives you fast access to devices, groups, automations, settings, and common actions—all without leaving your keyboard.
Wait for Input - Automation Action
Automation Action that waits for input from staff before proceeding.
Wait for Logged In User - Automation Action
Automation Action that will pause the pipeline and wait for a logged in user.
Automations UX Improvements
A variety of user experience improvements to automations
Patching - deny patches
Add the ability to deny specific patches from being installed.
Expanding Device Search Filters
Since Level.Io has a custom fields functionality, it would be great to be used as a search parameter when searching for devices. We have an ID for every device that the customer knows and it would make our work more efficient if we could just search by custom ID. This feature should also be included in the API.
SSO - Authentik
Add support for Authentik as SSO provider.
SSO - Okta
SSO Support for Okta as the IDP. This will allow users to log in to Level using their existing Okta accounts.
SSO - Google
SSO Support for Google as the IDP. This will allow users to log in to Level using their existing Google accounts.
API limitations
Currently the API does not allow for patching history, scheduling in the automation to accessed. It would be very helpful to have this available.