4807 results found
-
Logical Stacking/Grouping of Patch Versions
Feature Request: Patch Management Improvements
1. Logical Stacking / Grouping of Patch Versions
Issue:
Patch Management currently displays multiple versions of the same patch as separate items, leading to:- A cluttered list
- Difficulty identifying the latest relevant version
- Confusing or inaccurate reporting
- Inefficient patch evaluation workflows
Requested Enhancement:
- Introduce logic to group or stack all versions of the same patch under a single collapsed entry.
- Display only the latest applicable version by default.
- Allow users to optionally expand to see historical versions if needed.
2. Ability to Hide or Filter Out Specific Patches
Issue:
Customers cannot hide outdated or irrelevant…4 votes -
Date format API
The date format should generally be configurable, and in communication with the API, it should at least conform to ISO 8061
3 votes -
BackupPC
We would like to see some free options for backup/restore software, just like we have Splashtop or Anydesk for remote access.
6 votes -
Software Asset Tracking
We're looking for a way to store and manage software assets. For example, if we have 20 licenses of Adobe Acrobat, we would like to create the asset in Atera, know how many licenses we have, it's renewal date, and who the asset has been assigned to. This would be great for Microsoft 365, Atlassian, and other software licenses we need to track/manage.
It would also be great if we can upload contracts/documents with the asset.
27 votes -
MFA and logon control for small offices
Some program like DUO that will allow addition of controlled logon and MFA for small offices with no domain or other controls in place.
2 votes -
Contacts should include a Department Field
We have clients that require us to bill by Department. It would be great if the Contacts screen had an additional field, that displays right under the the Cusomer Name, "Department", so it is viewable on on the Ticket details screen in the Contact info area.
4 votes -
Greater variety of basic reports for non power accounts
The ability to generate simple reports for a client based on a singular category such as OS Version or a specific hardware specification such as the companies devices RAM capacity.
4 votes -
customer device view back
When viewing a device for a customer, there is no way to get back to customer devices. Going back goes to ALL devices. That's not funny for administer more devices of same customer.
1 vote -
Add departments in MSP
I need to use that: https://support.atera.com/hc/en-us/articles/4434393221148-Add-and-assign-departments
It's not possible in MSP account. Why? It's really usefull for big customers !
I need do cut a customer in subdivisions, and it's not possible. Incredible !3 votes -
ticket sentiment in API
Ticket Sentiment column is not exposed in API. When running reports, I cant get sentiment column for reporting the negative sentiment tickets
1 vote -
Integration with Vanta and other GRC's
Atera should consider integrating with Vanta because it would create a powerful synergy between IT management and compliance automation. Vanta is widely used for continuous monitoring and automated evidence collection to maintain security frameworks like SOC 2, ISO 27001, and HIPAA. By integrating with Atera’s RMM and PSA platform, MSPs and IT teams could seamlessly feed device, patching, and configuration data into Vanta, reducing manual work and improving audit readiness. This integration would not only enhance security posture but also deliver significant time savings for customers who need both operational efficiency and compliance assurance.
2 votes -
Ticket Titles Lost after Merging Tickets
Merged tickets have no history of their ticket titles. The ticket activity on the destination ticket just says "Ticket #40346 merged into this ticket" for example.
The conversation entries are preserved but often the ticket titles will have the crucial information for the issue and they are lost when the ticket is merged.
1 vote -
disable file transfer data showing for technician
I have disabled the File Transfer tab in the Atera console; however, it still appears to be visible and accessible to the technical team. For data security and compliance reasons, we need to ensure that no file transfer data is visible or accessible to technicians.
1 vote -
Include active ticket time entries in contract remaining hours before ticket resolution
At present, contract remaining hours are only reduced once a ticket is marked as completed or resolved.
This creates a planning and capacity issue for us managing multiple open tickets for the same customer. Time may already be actively logged against several tickets that are still in Pending or In Progress status, but the contract balance continues to show those hours as still available until closure.
As a result, the remaining hours shown can be misleading for operational planning and resource allocation. In scenarios where several tickets are resolved at the same time, the contract can suddenly move into over-usage,…
1 vote -
Folders/Organization for Ticket Automations and Patch Automations
We have a lot of ticket automations and patch management automations set up as every customer needs things set up a little different. Over time, this adds up and makes the automation pages feel very cluttered. It would be nice to have a way to organize these, ideally by customer. For ticket automations in particular, if it's broken down by customer, the ticket automations would only run for that customer. So, you could have general ticket automations and customer-specific ticket automations.
4 votes -
miradore
Miradore integration
2 votes -
Email notifications on Public notes when CCd
Currently no email notification is sent to a technician when they are mentioned in a Public note, this to me sounds like a simple request and is causing members of our team to miss ticket notes that they have been tagged in
1 vote -
Make the "Group" field on tickets visible on the Customer Portal
We would like the "Group" field on tickets to be visible on the Customer Portal view so our end users can see which team within our IT department is handling their ticket.
This helps because each team has their own set of SLAs and standards they follow, so it helps set better expectations and understanding with our end users when they have this information available to them.
1 vote -
Customer creation for level 1 techncians
We need non-admin users to be able to create Customers. We have custom roles created, and a lower level technician should be able to create a new customer, assign contacts and set them up. Deletion (or even better - archive, deactivate, or retire a customer) should certainly fall to an Admin role.
1 vote -
gili test
this is a test
2 votes
- Don't see your idea?