It would be extremely useful if Atera offered a way to define dynamic device groups. These groups could be created based on:

- Folder structures
- Naming conventions (e.g., Notebook*, Desktop*, Server*)
- Custom filters
- Manually assigned devices

Once defined, these groups could be used as target collections for various actions, including:

- Script execution
- Software deployment and removal
- Patch management
- Reporting and analytics
- Other automation tasks

This would allow administrators to perform recurring tasks across multiple customers, locations, or device types without having to repeatedly search for and select individual devices.

Practical Example
Today, I can use software reporting to identify devices that have an outdated application installed. I can also generate a list of all affected devices.
However, at that point the workflow becomes cumbersome. It would be much more efficient if I could:

1.) Select a predefined device group directly from the reporting interface.
2.) Scan only the devices that belong to that group.
3.) Immediately launch a script, software installation, or uninstallation task from the same dialog.

For example, if an outdated application is detected on devices within the "Notebooks" group, I should be able to directly initiate an update, uninstall, or remediation script against all affected devices without leaving the report.

Alternative Enhancement
Another valuable approach would be to allow actions directly from the software reporting results. After identifying affected devices, administrators should be able to:

- Select all or specific devices returned by the report.
- Run a script on those devices.
- Deploy software packages.
- Trigger automation profiles.

This would significantly reduce the number of steps required for software maintenance and remediation, streamline administration, and improve efficiency when managing large environments.

HOW IS THIS NOT A THING?

I have to create groups, per customer, where i add servers in, same for workstations. When a server/workstation is added, i have to put this in the correct group.
If a dynamic group is possible, this would save a great deal and less errors in the future.

Like more features i find Ciritical, this is one of them. And this feature doesn't seem to hard to make. But Atera knows this feature is needed sinds 2021....

Create group
where os name = server
make a script that can be run manually and one that runs every 24 hour, to update the dynamic group :)

I am new to Atera, and still getting to know all the features. We use devices attributes in intune like group tag. We already have dynamic groups for users and computers in Azure so those syncing to Atera would help. However it would be amazing as an example have Atera move a device to a site based on attributes or group. Then use either one to trigger an actions like a script.

I would also like to see some kind of movement on this. Samuel brings up a great point, our jobs are about building solutions for clients. If I build a script that starts a needed service for a widely used program like QuickBooks. I would want that script and threshold to apply to all servers that met some kind of profile. Lets say our profile can group all devices that are equal to "windows server" and has a program called "Quickbooks Database Server Manager". This solves the problem across all my clients including new clients that are brought on.

This would be so useful to patching and running scripts as with Win 11 21H2 going EOL if there was a dynamic group these machines could easily be upgraded to the latest version but at the minute i have to do each on manually because if i turn on upgrade windows 11 that will upgrade all the win 10 machines to Win 11, which we're not at a place to do yet.

Here's a good use case:

If I have a client that has my full package, I'll want to make sure they have my anti-malware package in addition to the RMM agent. To do this, I'll want to make a group that automatically adds computers which do not have the anti-malware software installed. Now when an endpoint becomes a member of this group I want Atera to run a script that I specify (this would be to install the anti-malware software). This way, I don't have to worry about whether endpoints have the software because it's being actively deployed precisely when it's required. Set it up and forget it.

This is such a big component of automation in the RMM space that so many overlook.

These groups can then be used to bill for devices when generating invoices.

Atera has a bunch of monitoring points and data it collects about an endpoint. I'd like to use that data to create dynamic groups. Essentially what I'm looking for is a way to create a group based on the filters available on the Devices page. When an endpoint meets the criteria of the group (or Device page search criteria), it should automatically become a member of the group I defined. When that same endpoint no longer meets the criteria of the group, it should be removed. These groups should be treated like the folders that are currently available, in that they can have Thresholds and IT Automation Policies applied to them, but these groups should NOT be tied to customers only - that should be specified in the group criteria.

This is really needed to simplify everything, another idea, which would be even more flexible, for Windows machines, when you deploy the agent, you can also deploy a GPO/Reg values, that will assign to the correct client/folder based on these settings

J

We would like to be able to use device filters in order to assign automation profiles. This could be one way to do it but a device would need to be able to be dynamically assigned to multiple folders.

Allow creating of folders based in filtered criteria (e.g. servers).

This way we don't have to remember to manually add new servers to the folder that is getting server based automation.

Add feature to group several customers and/or devices.
Also, add feature to apply a threshold profile or running a script on a group.

Just one example: Group that contains all servers, so I can apply a threshold profile or run a script on all servers at once.