- or
No existing idea results
- ~ No ideas found ~
4830 results found
-
IPAM & Rack Builder
Hi Atera team,
I would like to submit a feature request for two additions to the client documentation section:
IPAM (IP Address Management) — The ability to document and manage IP address allocations directly within a client's profile would be a significant improvement. This would allow MSPs to track used/available IPs, subnets, gateways, and device assignments without relying on external tools.
Rack Builder / Rack Diagram — A visual rack documentation tool integrated into the client profile would allow us to map physical infrastructure (switches, servers, patch panels, UPS, etc.) in a structured and visual way, making it much easier to maintain accurate and up-to-date network documentation.
Both of these features are currently handled through third-party tools like NetBox or Hudu, but having them natively in Atera would greatly streamline our documentation workflow and reduce context-switching.
Thank you for considering this request.
Hi Atera team,
I would like to submit a feature request for two additions to the client documentation section:
IPAM (IP Address Management) — The ability to document and manage IP address allocations directly within a client's profile would be a significant improvement. This would allow MSPs to track used/available IPs, subnets, gateways, and device assignments without relying on external tools.
Rack Builder / Rack Diagram — A visual rack documentation tool integrated into the client profile would allow us to map physical infrastructure (switches, servers, patch panels, UPS, etc.) in a structured and visual way, making it much easier…
2 votes -
Receive exported PDF of my scheduled patch management and IT automation via email
It's super easy to schedule a report on any Patch Management and IT Automation profile and get an email every day.
It would be soooo much more convenient and time-saving if you could get the export report in PDF format instead of a link directing you to the reports section.
Hope this can be added at some stage.
Thanks
Ronald1 vote -
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.
6 votes -
Tickets page new column
Add the ability to add a column showing total time logged to a ticket directly from the main tickets page.
1 vote -
Filtering on date fields (is null or is blank) unavailable
Currently, Atera does not allow filtering tickets or views by blank or null values in date fields, including built-in ones like Follow-up Date or custom date fields.
You cannot directly filter for tickets where the date is empty. There is no native functionality to filter by empty date fields or by today/tomorrow in custom date fields.
1 vote -
Tabbed or Minimisable devices view / Powershell / SSH sessions
I do a lot of remote PowerShell to work on various PCs. I have to open multiple tabs of Atera to work on different PCs at the same time. I would like the ability to open a remote PowerShell, then minimize it and open remote PowerShell on multiple other PCs at the same time within one window. That way, it can continue to run the command minimized while I work on something else, and can check back on it later to see if it finished.
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.
29 votes -
Trouble Ticket Detail Templates
I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text, including headings, bullet points, hyperlinks, and styling (bold/italics)Optionally dynamic fields like [Customer Name], [Device], [Technician], etc., to auto-fill standard variables
User Experience:
When a template is selected, its content would populate the Description field automatically, which the technician can then tweak or expand upon.Markdown or basic WYSIWYG formatting should remain available.
Why This Matters:
Time-saving: No more copying and pasting from external documents or previous tickets.Consistency: Ensures all tickets follow the same structure, improving technician clarity and client-facing professionalism.
Training: Makes onboarding easier for new techs who can follow standardized ticket language and formatting.
Compliance and QA: Helpful for meeting internal documentation standards or industry compliance by enforcing specific data formats.
Example Templates:
Initial troubleshooting checklist
Onsite visit summary template
Firewall install/config notes
End-of-shift handoff summary
Service outage postmortem formatOptional Enhancement:
Allow default templates to be tied to specific ticket types or categories (e.g., selecting “Onsite Visit” from ticket type preloads the corresponding template).I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text,…15 votes -
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…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 -
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, despite the work having been carried out gradually over time.
Please allow contract remaining hours to reflect all logged time entries immediately, regardless of ticket status (Open, Pending, In Progress, or Resolved).
Alternatively, a separate field such as “committed / logged unbilled hours” or “projected remaining hours” would also help accurately forecast contract usage before ticket closure.
This would significantly improve workload planning, prevent accidental contract overruns, and provide a more accurate real-time view of customer support hours.
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
- Don't see your idea?