Create groups to organize your devices according to their technical parameters. Device groups are dynamic, based on filters, and you can assign Threshold and IT automation profiles to them. 

Unlike folders, which let you manually place a device in a single location with one set of rules, dynamic groups are defined by filter conditions and membership is updated automatically. 

It means you can add a device to multiple groups at once, each carrying its own Threshold and IT automation profiles, so you can act on all its different properties simultaneously. 

Why use dynamic groups?

• No manual membership upkeep: Devices join or leave a group instantly as their properties change, no manual reassignment needed. 

  E.g. A newly provisioned laptop matching a "Windows 11" group will be added to it the moment it comes online.

• Layered monitoring: A device can belong to multiple groups at once, each with its own Threshold profile, so all aspects of the device are monitored on their own terms.

  E.g. A workstation can hold a strict memory profile from one group and a standard baseline from another simultaneously.

• Live automation targeting: IT automation profiles read group membership at execution time, not at assignment, which means relevant devices are always covered.

  E.g. A device that upgrades its OS build is picked up by the next automation run without requiring any manual step.

• Custom grouping conditions: Customer and agent custom fields become filter conditions, letting you group by attributes Atera doesn't expose natively. 

  E.g. A "Compliance state" field updated by a script becomes a live group that a remediation profile targets automatically.

Static folders vs. Dynamic groups

Folders and dynamic groups complement each other rather than replace one another. Folders are useful for stable hierarchical structure, and dynamic groups take over where device properties define the target. Use them together for the most flexibility. 

For more information about folders, see Use folders to manage devices.

Before you begin

Take note of the following: 

• A group can include agentless devices (SNMP, HTTP, TCP, and Generic), but Threshold and IT automation profiles will only apply to devices with an agent installed. 
• A group is only as accurate as the field behind it. For example, custom field-based groups depend on those fields being kept current.
• The following filters are not supported and will prevent you from saving a view as a group if selected:
  • Filters: SNMP type; Availability
  • Advanced filters: Last reboot; Last seen; Available patch; Installed patch; Available patch class; OS patching status; Installed software; Software patching status; Work from Home; agentless Custom fields; time-based Custom fields.

Create a Dynamic group

Build a group from the Devices page by filtering your device list and saving the filtered view as a named group. The filter conditions you add will become the group's live definition.

To create a dynamic group: 

1. From your navigation panel, go to the Devices page and click Filters.

2. Select the filters you want to group your devices by.

3. (Optional) Click Advanced filters to add more filters. Then click Apply.

Note: Conditions combine with AND/OR logic, letting you build precise, reusable groups. 

For example: OS version = Windows 11 AND (Memory = 16 GB OR Memory = 32 GB).

5. Click the Save button next to the Default view dropdown at the top left of the page. 

6. Switch the toggle to Group and enter a name in the Group name field. Then click Save.

Your group now appears in the Default view dropdown.

Assign an IT automation profile to a group

Assign an IT Automation Profile to a group to target devices based on their current properties. Group membership is read live at execution time, not frozen at assignment, so the right devices are always covered as they join or leave the group.

Note: Multiple automation profiles can target the same device through different groups. If their actions contradict, they will still run as there is no automatic deconfliction.

To assign an automation profile to a group:

1. From your navigation panel, go to Admin > Monitoring and automation >  Patch management and IT automation.

2. Click the three dots icon () next to the profile you want to assign, then click Assign.

3. Click the Groups tab and select the groups you want to assign this profile to from the Assign to groups dropdown. 

4. Click Save. 

The profile is assigned. It applies to all current and future members of the group(s).

Assign a Threshold profile to a group

Assign a Threshold profile to a group to apply it to every device in that group. A device can belong to multiple groups at once, each with its own Threshold profile, so all device properties can get tailored treatment.

Note: Since a device can receive threshold profiles from multiple groups, when monitored items overlap, the most recently edited profile's items take effect. There is no manual priority setting.

To assign a threshold profile to a group:

1. From your navigation panel, go to Admin > Monitoring and automation > Thresholds.

2. Click the the dot icon () next to the profile you want to assign, then click Assign profile.

3. Click the Groups tab and select the groups you want to assign this profile to from the Assign to groups dropdown. 

4. Click Save. 

The profile is assigned and applies to all current and future members of the group(s).

Conflict handling

• When a device belongs to multiple groups, overlapping monitored items can result in conflicting actions being executed:
  • Threshold profiles: Last edited policy wins. E.g. If profile A was assigned first but edited after profile B, profile A's settings apply to the overlapping items. 
  • IT automation profiles: Both policies execute. E.g. If Profile A installs a software update but Profile B uninstalls it, both actions will still run.
• When a device leaves a group, the group's assigned profiles stop covering it. 
• If you delete a group that has profiles assigned, the association breaks—any device that was covered through that group loses the profile assignment.

Use cases

#1 Cross-site OS upgrades: You need to upgrade all Windows 10 devices to Windows 11, but they're spread across multiple sites. Create a group for all devices running Windows 10, and scope the group to specific sites or apply it across all of them. Assign an upgrade automation profile to it. Membership updates as the rollout progresses, so the group shrinks automatically.

#2 Compliance targeting: Some devices in your environment aren't meeting security requirements, but identifying and targeting them manually is time-consuming. Use a script to write a compliance state into an agent custom field, then create a group based on that field. Assign a remediation IT automation profile to the group; it reads live membership at every run, so newly non-compliant devices are picked up without any manual step.

#3 Multi-department memberships: An employee supports two departments and needs software from both, but they can only sit in one folder. Tag their device with two agent custom fields (one per department) and create a group for each. Since the device matches both groups, it receives the software policies assigned to each automatically. No duplication, no manual overrides.

FAQ

Q: Do dynamic groups replace folders?

A: No, they complement folders. Folders are useful for stable organizational structure. Dynamic groups are intended for attribute-based or compliance-driven targeting.

Q: Can a device be in more than one group?

A: Yes, through multiple group memberships. If a device answers all the filters conditions you selected, it will become part of the group.

Q: Can I group by patch status or installed software?

A: No. Patch and software inventory fields are not supported filter conditions for dynamic groups. See the full list

Q: What if two IT automation policies on one device contradict?

A: Both run. There is no auto-deconfliction, so we advise reviewing automation assignments across overlapping groups to avoid conflicts.

Q: Can a device receive multiple Threshold profiles?

A: Yes, if it is part of more than one group. When monitored items overlap, the most recently edited assigned profile wins for those items.

Q: What happens when a device no longer matches a group's conditions?

A: The device automatically leaves the group, and the group's assigned profiles stop covering that device.

Q: What if I delete a group with profiles assigned?

A: The association breaks. Those profiles still exist but they no longer apply through the deleted group.