Skip to main content

Getting Started with Level

An introduction to Level — what it does, how it's organized, and where to go first.

Updated this week

Introduction

Level is a browser-based RMM platform for managing Windows, macOS, and Linux devices. Install the Level agent on a device, and you can monitor it, access it remotely, run scripts, push updates, and automate routine tasks — all from the web interface.

This article orients you to the platform. The other Getting Started articles walk through each setup step in detail.


What You're Looking At

Level Dashboard

The left sidebar is your main navigation. Here's the short version of what each section does:

  • Devices — Your managed device inventory. Every enrolled device shows up here. Click any device to open its detail view.

  • Updates — Global patch status across all devices.

  • Alerts — All active and resolved alerts from your monitors, across all devices.

  • Reporting — Built-in reports for device health, patch compliance, and more.

  • Automations — Automated workflows built from triggers and actions. This is where scheduled tasks, event-based responses, and onboarding sequences live.

  • Scripts — Your script library. Scripts you save here are available inside automations and for on-demand runs.

  • Files — File storage used by automations to deliver files to devices.

  • History — Log of automation runs, script executions, and other activity.

  • Monitors — Monitor policies that watch for issues and fire alerts.

  • Workspace — Global configuration: tags, team members, custom fields, permissions.

  • Settings — Account, organization, integrations, API keys, webhooks.


How Level Is Structured

Three concepts underpin how everything fits together: devices, tags, and automations.

Devices are any machine with the Level agent installed. They can be organized into device groups for easier management, but grouping is optional — tags do most of the heavy lifting.

Tags classify devices. When you tag a device "Workstation" or "Server," that tag becomes a targeting handle. Monitor policies, automations, and other configurations all target devices by tag rather than by individual device or group. Get your tagging right early and everything downstream gets easier.

Automations do the work. Scheduling updates, tagging new devices on enrollment, running security checks, prompting users before reboots — all of that happens through automations. New accounts come with a pre-built set in the Get Started group so you don't have to start from zero.


🎬 Video Walkthroughs

Platform Overview

Introduction to Automations


Where to Go Next

Work through these in order when setting up a new Level account:

  1. Adding Devices, Groups, and Tags — Install the agent and get your first devices enrolled. Set up your tag structure.

  2. Review Starting Automations — Level pre-populates your account with ready-to-run automations for patching, tagging, and more. Enable what you need.

  3. Review Monitors — Your account includes a default monitor policy. This article walks through what's included and how to adjust it.


FAQ

  • Do I need to set up anything before devices start appearing? Yes — you need to install the Level agent on each device. The agent handles enrollment automatically once installed. See Standard Install for per-platform instructions.

  • Can I manage devices without organizing them into groups? Tags handle most targeting in Level, so groups aren't required to get started. Groups are useful for applying permissions and defaults at a team or client level, but you can tag and target devices without them.

  • What's the difference between Monitors and Automations? Monitors watch for conditions and generate alerts when something's wrong. Automations respond to events (including alerts) and take action. They work together — a monitor fires an alert, and an automation can respond to that alert automatically.

  • Who should I contact if something isn't working? Reach out to Level support at [email protected] or use the in-app chat.

Did this answer your question?