Skip to main content

Groups

Organize devices into groups and subgroups to structure your devices and control technician access.

Updated this week

Introduction

Device groups organize your devices and control which technicians can access which devices. Every device belongs to a group, and access is granted at the group level β€” so how you structure groups directly shapes how your team works.


🎬 VIDEO


Device Groups

Groups are containers for devices. They're hierarchical β€” you can nest groups as deeply as you need β€” and they're the primary way technicians are scoped to parts of your environment.

Selecting a group in the sidebar filters everything in Level to that group: the device listing, pending updates, active alerts, and reports all scope to whatever group you've selected. Select All devices to return to the org-wide view.

πŸ’‘ TIP: For details on filtering and navigating with groups, see Device Listing.

Internal IT vs. MSP

How you structure groups depends on how you use Level.

Internal IT teams typically organize by location, department, or function β€” something like:

  • Headquarters

    • IT

    • Finance

    • Human Resources

      • Benefits

      • Recruiting

  • Remote

MSPs typically create one top-level group per client, then add subgroups to reflect that client's internal structure as needed:

  • Acme Corp

    • Workstations

    • Servers

    • Infrastructure

  • Widgets Inc

    • Executive

    • Finance

Either way, the structure is flexible. You can nest groups as deeply as needed, rename them at any time, and restructure as your environment changes.


System Groups

The top of the sidebar shows four system groups. These are fixed β€” they can't be renamed or deleted.

  • All devices β€” Every device in your organization

  • Favorites β€” Devices you've personally starred. Favorites are per-user and not visible to your team.

  • New devices β€” Devices that checked in for the first time within the last 7 days

  • Ungrouped devices β€” Devices not yet assigned to a group

ℹ️ NOTE: Only organization admins can see ungrouped devices.


Creating Groups

To create a new top-level group:

  1. In the sidebar, click the + icon next to DEVICE GROUPS.

  2. Enter a name for the group.

  3. Press Enter or click Save.

To create a subgroup inside an existing group:

  1. Hover over the parent group in the sidebar.

  2. Click the three-dot menu that appears on the right.

  3. Select New subgroup.

  4. Enter a name and confirm.

Group Options

Groups are listed alphabetically within each level of the hierarchy.


Managing Groups

Hover over any group in the sidebar to reveal its three-dot menu. Options:

  • New subgroup β€” Add a child group under this one

  • Move to... β€” Relocate this group within the hierarchy

  • Settings β€” Open the group's configuration

  • Rename β€” Change the group name

  • Delete β€” Remove the group

⚠️ WARNING: A group can't be deleted while it contains devices or has automations linked to it. Move or reassign all devices first, then unlink any automations before deleting.

Moving Groups

Move to... lets you reposition a group within your hierarchy β€” making it a subgroup of another group, or promoting it to the top level. The group's devices, subgroups, and settings all move with it.

Renaming Groups

Renaming a group updates it everywhere in Level immediately β€” in the sidebar, on device rows, and in any automations or reports that reference it.


Group Settings

Each group has a settings area with dedicated tabs for configuration. Access it by hovering over any group in the sidebar β†’ three-dot menu β†’ Settings.

The settings tabs are covered in their own articles, but here's what each one does:

  • Settings β€” Rename the group and configure group-level defaults. See Group Settings β†’ Settings.

  • Custom Fields β€” Set group-level default values for custom fields. These cascade down to devices in the group unless overridden at the device level. See Group Settings β†’ Custom Fields.

  • Linked Automations β€” View all automations referencing this group via a trigger, action, or condition. A group with linked automations can't be deleted until those automations are removed or updated. See Group Settings β†’ Linked Automations.

  • Security β€” Configure remote control approval behavior for devices in this group. You can require end-user approval before a technician can connect, or allow connection with just a notification. Settings are inherited from the parent group by default and can be forced down to all subgroups. See Group Settings β†’ Security.

  • Permissions β€” View which technicians have access to this group, its subgroups, and all devices within them. Shows each technician's name, title, and role. To adjust roles or permissions, follow the link to the Permissions page. See Group Settings β†’ Permissions and Workspace β†’ Permissions.

ℹ️ NOTE: Technicians only see devices in groups they've been granted access to. If you need to restrict or expand a technician's access, that's managed in Workspace β†’ Permissions.


FAQ

  • What's the difference between groups and tags? Groups control structure and access. Tags drive automations and monitoring policies. A device belongs to one group (or nested group hierarchy); it can carry as many tags as needed. Use groups to organize your devices and scope technician access, use tags to target automations and monitors.

  • Can I move a device between groups? Yes. From the device listing, select the device, click Assign to group, and choose the destination. You can also do this in bulk β€” select multiple devices and assign them in one step.

  • Can I nest groups as deeply as I need? Yes, there's no depth limit. That said, very deep hierarchies can become hard to navigate. Most teams find two to three levels covers most use cases.

  • What happens to devices if I delete their group? You can't delete a group that still contains devices. Move all devices to another group first, then delete.

  • Why can't I see a device in the listing? If a device isn't in any group you have access to, it won't appear. Ask your Level admin to check group permissions for your account β€” see Workspace β†’ Permissions.

  • Who can create and manage groups? Organization admins can create, rename, move, and delete any group. Technician permissions vary by role and may be restricted to specific groups. See Workspace β†’ Permissions for details.

Did this answer your question?