- or
No existing idea results
- ~ No ideas found ~
4710 results found
-
Can ticket automation do follow-ups and close if no answer?
We've been trying to find a way to implement automated tickets follow-ups (using "activity status" and "hours since status changed") but can't seem to get it to work. Has anyone been able to make it happen? Currently, there is no trigger for Activity Status just Status. We cannot mark the ticket as Pending everytime to trigger this automation. Defeats the purpose of an automation it will have be done manually. I found a reddit article replied by Atera (3 years ago) and still no change. https://www.reddit.com/r/atera/comments/zevva9/can_ticket_automation_do_followups_and_close_if/
1 vote -
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 patch versions, resulting in:- Noise in the patch list
- False perception of devices being out of compliance
- Manual work to track what’s relevant
Requested Enhancement:
- Allow users to hide selected patches or categories of patches from visibility.
- Option to mark a device "up to date" regardless of deprecated patch entries.
3. Bulk Exclusion of Patches (Keyword-Based or Multi-Select)
Issue:
Excluding patches must be done one version at a time, which is extremely time-consuming—especially for vendors like Intel, Dell, or HP where dozens of minor revisions appear simultaneously.Requested Enhancement:
Provide multiple bulk-exclusion options:- Keyword-based exclusion (e.g., exclude all patches containing “Intel Extension”, “Dell Firmware”, etc.).
- Multi-select UI (checkboxes) to exclude many patches at once.
- Bulk actions (exclude, hide, group, etc.) for selected patches.
4. Improved Patch Display Customization
Issue:
Customers want more control over which patch categories or vendors appear, so only relevant updates surface.Requested Enhancement:
- Allow filtering or toggling by vendor, patch type, severity, or category.
- Offer a simplified “clean view” showing only meaningful, actionable patches.
5. Enhanced Reporting Accuracy
Issue:
Reporting is skewed by the presence of older patch versions being listed as "missing," even when newer superseding patches exist.Requested Enhancement:
- Update reporting logic to reflect supersedence and the latest required version.
- Ensure that hidden/excluded versions no longer impact compliance scores.
6. Roadmap Visibility for Patch Management Improvements
Issue:
Customer is in renewal evaluation and expressed frustration; they need clarity about whether patch usability improvements are planned.Requested Enhancement:
- Provide a public or semi-public roadmap note indicating upcoming Patch Management enhancements.
- Offer improved internal communication on how these FRs progress through Product review.
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…3 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.
21 votes -
How do I download and install the QuickBooks Tool Hub safely?
To download and install the QuickBooks Tool Hub, first download the most recent version (1.6.0.8) of it from the official website. Then, open the QuickBooksToolHub.exe file you downloaded, and follow the guide on your screen to install it.
5 votes -
Granular Hardware Mapping (Slots & Ports)
We need Atera's RMM agent to natively report granular physical device information. Currently, we cannot automatically determine which RAM slots (DIMMs) are occupied/free, or get a detailed mapping of connected controllers (USB, SCSI, IDE) and their corresponding slots and ports. This data is critical for accurate remote inventory management, planning hardware upgrades, and troubleshooting port-level issues without requiring a physical check. Please implement a native function to capture and display this data on the asset page.
4 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.
3 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.
3 votes -
Signature ios
Add signature options to mobile apps for technicians. Currently it doesn’t pull them through from profile so responses done on mobile app don’t include a signature
2 votes -
API for emails to pull tickets in via API calls rather than forwards or SMTPAuth
An option to integrate with email providers i.e. Microsoft via API calls rather than forwards.
This would allow emails/tickets to be pulled in fast, secure and minimises the amount of issues that can arise from email forwards and can help prevent ETP systems from double scanning emails that have already been checked (reducing hops and preventing further delivery issues)
2 votes -
Ticket Forms, under type, Dropdown with dependencies, it would be nice to multiple child levels.
When creating new ticket forms and selecting a dropdown with dependencies, there is only one child layer option. It would simplify our setup if we could include multiple child levels. I have attached an example of the current option and the desired option.
2 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
2 votes -
Patch Management Alerts if more than xx updates
An alert is created when a customer or device has more than xx number of patches. This would indicate that the device is failing to run patches/offline and requires investigation.
The idea would greatly assist us as the current schedule report takes so long to go through with so many devices to check
37 votes -
azure department
Include the department as a sync'd field with Entra ID integration
4 votes -
Agent-reported device name synchronisation
Hi Atera team,
First of all, I just want to say how impressed we are with the platform. The pace of development, the clarity of the API, and the overall reliability of the agent have made Atera a core part of how we operate day to day. It’s clear a lot of care has gone into building something that scales well for real-world MSP use.
We wanted to raise a small but potentially high-impact feature request around device naming and agent reporting.
At the moment, if a device hostname is changed locally at the OS level, that change does not appear to propagate back into the Atera dashboard or API. As a result, fields such as AgentName, SystemName, and MachineName remain static against the AgentID / DeviceGuid, even though the underlying system identity has changed.
It would be incredibly valuable if the agent could report the current OS-level device name back to the tenant on check-in and update those fields automatically.
This would unlock several practical benefits for all Atera users:
Improved estate accuracy
Device inventories would remain aligned with the actual environment, reducing drift between reality and the dashboard over time.Cleaner automation and integrations
Many workflows, scripts, and third-party integrations rely on device names as human-readable identifiers. Keeping names in sync removes ambiguity and manual reconciliation.Reduced operational overhead
MSPs would no longer need to manually correct naming mismatches after rebuilds, renames, or standardisation exercises.Better reporting and analytics
Accurate naming improves confidence in reports, audits, and compliance checks, especially in larger or more dynamic estates.Smoother onboarding and lifecycle changes
Device renames during provisioning, repurposing, or role changes would naturally flow through without additional admin effort.From a data model perspective, this feels like a natural extension of the excellent work already done around agent telemetry, with the AgentID / DeviceGuid remaining the stable anchor while human-readable identity stays current.
We appreciate that there are always trade-offs and edge cases to consider, but this feels like a change that would quietly improve quality of life across the entire platform.
Thanks again for building such a solid product, and for being consistently open to feedback from the community. We’re very happy Atera users and excited to see how the platform continues to evolve.
Kind regards,
IanHi Atera team,
First of all, I just want to say how impressed we are with the platform. The pace of development, the clarity of the API, and the overall reliability of the agent have made Atera a core part of how we operate day to day. It’s clear a lot of care has gone into building something that scales well for real-world MSP use.
We wanted to raise a small but potentially high-impact feature request around device naming and agent reporting.
At the moment, if a device hostname is changed locally at the OS level, that change does not…
2 votes -
Device Info History - Hostname, Logins, Reboots
There are many ideas like this one, but they are limited to very specific things - most of them targeting the user history.
We need more than just user history, we need ALL history. Most things on the Overview page should have their own history tracking. Sure, things might be tracked in the activity log - but sometimes we need very specific information that may not be logged at all.
First and foremost, every one of these fields should have a little icon next to them to display the history of the field. You will also note I have included an additional field, called 'Device hostname', because the simple fact is you can change the name of a device in Atera completely different than the hostname of the device... but both are important, and thus should not be ambiguous.
Device name
Device hostname
Domain
Public IP
Last login
Last rebootFurthermore, it would be good to see the history for the owner info:
Customer
Folder
ContactAnytime a new field is added here, it should also be considered for history tracking. Perhaps there should be a limit on things like 'Public IP' and 'Last reboot' history, but that can easily be an internal setting in the admin console or set to a number that nobody would have a problem with, like 30.
There are many ideas like this one, but they are limited to very specific things - most of them targeting the user history.
We need more than just user history, we need ALL history. Most things on the Overview page should have their own history tracking. Sure, things might be tracked in the activity log - but sometimes we need very specific information that may not be logged at all.
First and foremost, every one of these fields should have a little icon next to them to display the history of the field. You will also note I have included…
3 votes -
Ubiquiti Integration
Ubiquiti Integration
960 votesHi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
-
Wildcards in searches
"While the global search has been enhanced to be a fuzzy search, and also now includes custom fields, searches in general are still missing proper wildcards.
First and foremost, I would like to see the common '' and '?' wildcards honored. Even the advanced filters lack this ability, only providing the 'contains' which is just a poor man's wildcard providing the basic '<search>*' option.
Bonus points if you will implement a RegEx function in some way... whether it is a checkbox next to the search box or initiated by some special character combination, such capabilities deserve to be available in the main UI instead of the just the advanced reporting system."
"While the global search has been enhanced to be a fuzzy search, and also now includes custom fields, searches in general are still missing proper wildcards.
First and foremost, I would like to see the common '' and '?' wildcards honored. Even the advanced filters lack this ability, only providing the 'contains' which is just a poor man's wildcard providing the basic '<search>*' option.
Bonus points if you will implement a RegEx function in some way... whether it is a checkbox next to the search box or initiated by some special character combination, such capabilities deserve to be…
1 vote -
Please BRING BACK CHAT button, so we dont have to connect to discuss support!
We would love to be able to pop open a chat window with a user w/o third-party apps.
This would prevent unnecessary take-overs, accidental inputs, and simplify comms.
1 vote -
Ability to schedule already open tickets
I have recently discovered that a few clients will have a ticket open already and will not reply for a few days and then ask to have the issue looked at on a specific day.
This wouldn't be too bad if there wasn't already key details and notes in the ticket already, and closing and opening is just tedious as the ticket isn't technically closed/resolved.
I feel like a feature to schedule an already open ticket to automatically be closed and reopened within a specific time frame would be amazing.
It doesn't even need to be necessarily closed, just disappear from the list of open tickets (until the time frame, and it would then automatically appear back in the list). Kind of like how you can snooze alerts for a specific time - can this be implemented for tickets?
Maybe it's just my OCD but I hate seeing open tickets that are just waiting and collecting dust.
This shouldn't be too hard to implement as there is already a schedule ticket button when creating one - just allow that feature on an already open ticket.I have recently discovered that a few clients will have a ticket open already and will not reply for a few days and then ask to have the issue looked at on a specific day.
This wouldn't be too bad if there wasn't already key details and notes in the ticket already, and closing and opening is just tedious as the ticket isn't technically closed/resolved.
I feel like a feature to schedule an already open ticket to automatically be closed and reopened within a specific time frame would be amazing.
It doesn't even need to be necessarily closed, just disappear…30 votes -
Add email snippet to put in a template that takes the agent to the ticket
Add email snippet to put in a template that takes the agent to the ticket
1 vote
- Don't see your idea?