What we’re building

Level roadmap

See what’s planned, what’s up next, and what we’re building now.

Roadmap stage

Planned

5

Up next

8

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.

1 vote

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.

2 votes

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.

11 votes

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.

0 votes

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.

1 vote

Add common diagnostic actions to automations

As a technician, I want to add prebuilt diagnostic actions to an automation so that when a monitor triggers an alert, I can collect evidence from the affected device without writing or maintaining custom scripts. For example, when a low disk space monitor fires, the automation could collect a disk report showing which volumes are running low and which directories are using the most space. A technician could then review the report alongside the alert and decide what to do next. Each action should work across Windows, macOS, and Linux. Technicians should be able to select the same action for any supported device and get a clearly labeled report with the details available on that platform. Proposed actions Collect Resource Report — Show CPU and memory usage and identify the processes using the most of each. Collect Disk Report — Show total and available space by volume and identify the largest directories on the affected volume. Collect Service Report — Show the status of selected services, whether they are configured to start automatically, and any recent failures. Collect Recent Logs Report — Gather relevant system or application log entries for a configurable time window around the alert. Additional actions to consider Collect User Report — Show active user sessions and recent sign-ins to help investigate login or session issues. Collect Application Report — Show installed application versions and recent installs or updates to help identify software changes that may be related to the alert.

0 votes

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.

0 votes

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.

3 votes

In progress

4

Remote Control Chat

The Remote Control Chat feature allows technicians to communicate directly with end users during remote sessions. This streamlines troubleshooting by keeping conversations within the session, improving clarity, and enhancing the support experience without needing separate communication tools.

102 votes

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.

84 votes

🔒 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.

8 votes

Ability to move/copy Monitors between different Monitor Policies

We have several Monitor Policies set up that target different groups, like "All Workstations", "BYOD", Company-Owned", etc. I'd love to have the option for moving or copying a Monitor between those different policies. Use cases: 1. I create a Monitor in our "Test Monitors" Monitor Policy where I test Monitors with a small workstation test group before expanding it out to the larger fleet. Once I validate the Monitor, it'd be nice to be able to move or copy it to the production Monitor Policy instead of needing to carefully re-create it in the production Monitor Policy without accidentally misconfiguring it differently from what I already validated with the test group. 2. Specifically for the copy feature. Once I validate a new monitor, sometimes it's necessary to have some but not options tweaked between our different Monitor Policies. E.g. some Monitors need to be slightly changed when used on BYOD workstations vs. Company-Owned. It'd be great to be able to copy a Monitor to a different Monitor Policy so that just those settings can be tweaked instead of needing to recreate the whole thing.

1 vote