- or
No existing idea results
- ~ No ideas found ~
4765 results found
-
Kill Splashtop SOS sessions
Terminate Splashtop SOS sessions directly from Atera when the session limit message appears, instead of waiting one hour for them to expire automatically
2 votes -
Ticket tabs "more"
When there are more than (on my screen) 13 ticket tabs open, you get a "x more" (x being a number) stack to the right.
I cannot find an option to close open tabs in that list.
Please add an "x"-Button next to ticket title in that list.2 votes -
Make all custom fields available in scripts
Currently only agent custom fields are available to use in scripts. All custom field should be available (where sensible). For example, customer wide custom field containing data we want to access in a script.
5 votes -
Webhooks
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the system should be capable of doing the following:
We would like to be able to trigger Webhook calls on alert creation and resolution events. We do not want to use Zapier as Freshservice has a listener element where the Atera hook can be launched, and using Zapier would unnecessarily increase steps and operational costs.
This functionality (attaching Webhook calls to alert creation and resolution events) would be the cleanest and most effective way to keep alerts connected between the two systems and ensure we don’t miss anything.
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the…
12 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
-
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…
6 votes -
Restrict the ability to set Closed Status on Tickets
Since "Closed" status permanently closes a ticket without giving the requester the ability to re-open it, I'd like the ability to remove the "Closed" status from the Status dropdown box.
The workflow we want to have is a technician sets a ticket to "Resolved" and then an Atera rule automatically changes Resolved tickets to Closed after a period of time which can be done. However technicians are accidentally setting tickets to "Closed" and duplicate tickets are being created when a requestor immediately replies.
I know there's an option to allow "Closed" tickets to be re-opened, however I do not want to enable that option. So we can better track repeat issues, requesters not responding and putting in more tickets later/using more of IT's time, etc.
The Data Management > Custom Fields page does not allow you to change anything about the built-in status values.
Since "Closed" status permanently closes a ticket without giving the requester the ability to re-open it, I'd like the ability to remove the "Closed" status from the Status dropdown box.
The workflow we want to have is a technician sets a ticket to "Resolved" and then an Atera rule automatically changes Resolved tickets to Closed after a period of time which can be done. However technicians are accidentally setting tickets to "Closed" and duplicate tickets are being created when a requestor immediately replies.
I know there's an option to allow "Closed" tickets to be re-opened, however I do not want…
1 vote -
Centralized Report Scheduling
A centralized way to schedule reports to their receivers so they aren't tied to specific technician as that solution is not manageable in the long run. Managing customer facing reports shouldn't be tied to a single technician and automation/scheduling on reports would be beneficial to be open to all technicians or tied to a role.
2 votes -
Device Search
We name our devices in Atera based on Site and User. However, the devices themselves are named by their asset tag. When I search in Atera under Devices in EITHER category by device name it does not find it and the name is clearly in the information Atera gathers about the device. This is frustrating - please fix.
1 vote -
"Update all" button on Devices page
I believe there should be a button within the navbar of the Devices tab that once selecting specific machines, allows you to update all patches on those machines, rather than doing a report, manually clicking all unnecessary machines or doing it patch by patch on the Patch Management page.
55 votesHi,
Thank you for your valuable suggestion. While we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
We continuously review user feedback to inform our development priorities, so your idea remains on our radar.
Best regards,
The Atera Team
-
OTP
OTP should NOT be required for paid accounts.
OTP for trial accounts is understandable to prevent abuse, but requiring OTP for interactive installs for paid accounts is not a good idea and can severely inhibit normal, legitimate deployment of the agent.
Please consider limiting this requirement to trial accounts only.
2 votes -
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 -
Automatically close Alert tickets when resolved
Would be really helpful to have alert tickets automatically close when the alert is resolved
For example Machine status unknown ticket closes when machine is back online!215 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 -
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 -
Notes field should be visible and searchable from the main devices page
It should be visible (selectable from Edit columns on Devices page) and searchable from the main devices page, so I can add something like the location (ex. Tom's Office) or who the user is and I can quickly find that computer based on my comment.
4 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
- Don't see your idea?