- or
No existing idea results
- ~ No ideas found ~
4830 results found
-
Atera Autopilot (Robin) needs access to reply with user's mobile number for verification
Atera Autopilot (Robin) currently doesn't have the ability to access a user's Mobile Number. This would be helpful when a user tries to perform a password reset so Autopilot can ask them to verify the number so they know it will be sent to the correct mobile device. The whole number does not have to be displayed, you could display just the last 4 digits or so of the number and ask the your to verify if it is the correct number before sending the reset password to it.
1 vote -
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 -
Ability to set default ticket form by customer
Please add the ability to set default ticket form by customer.
for MSP's customers have different requirements and needs. I have customers who require users to answer questions like "Problem Type" and the user can select "Website" or "ERP" which we can use to assign the ticket to the correct person/team or report on. i don't want that showing for every customer and i don't want to have a dropdown for "Select ticket form" that can show my customers that i have other customers.1 vote -
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 -
Asset Depreciation Tracking Based on Cost and Year Usage
Description: Add a native feature to calculate and track depreciation of IT assets based on purchase cost and age. Admins should be able to set depreciation method (e.g., straight-line), useful life, and view current book value. Include exportable reports for finance and budgeting purposes.
Use Case: Supports financial planning and asset replacement strategies by providing real-time depreciation data.
6 votes -
Ubiquiti Integration
Ubiquiti Integration
969 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
-
Printers Detail Tab Under Devices
Add a "Printers" tab to the device view in Atera. This tab would show a list of all printers configured on the workstation, with relevant details such as printer names, IP addresses, installation type (for example, group policy deployment or manual setup), and status. Having this information easily available would streamline troubleshooting and provide a more complete picture of each device's configuration.
3 votes -
Inject passwords into remote session
Create an easy way to inject passwords stored in the atera device tab to be injected into a splashtop session to be more efficient and reduce the time it takes to log into windows sessions. A password vault that can be injected into the session without having to copy and paste.
3 votes -
Request for Ability to Query Technicians via API
I’d like to request support for querying technician data through the API and/or within exportable datasets. Currently, there doesn’t appear to be a way to retrieve a list of technicians or their associated details programmatically. This creates challenges when building automations, permission audits, onboarding/offboarding workflows, and integrations that rely on technician information.
2 votes -
Request for Larger Page Limits When Querying Tickets, Customers, Alerts, etc.
I’d like to request an enhancement to the API/UI regarding data retrieval limits. Currently, when querying items such as tickets, customers, alerts, and other objects, the page size limits are quite restrictive. This creates unnecessary overhead, especially for larger environments where we need to pull or review substantial datasets.
3 votes -
Display a tickets details on the "New Child Ticket" or "New Parent Ticket" screens
When creating a child or parent ticket from within an existing ticket, I click "New child ticket," which opens the "New ticket" window. But I sometimes forget to check the site, user, priority, etc. before clicking "New child ticket" and the info isn't displayed anywhere in that new window.
If I click "Cancel" to go back to the existing ticket to copy the info, for some reason it doesn't take me back to the existing ticket I was just in. Instead it takes me to the default "All Tickets" page.
From there I have to find the existing ticket again, click into it, be certain I've got all the info from the existing ticket I'll need for the new ticket, click "New child ticket" again and THEN manually enter the duplicate info.
It would be much easier if, when someone created a child ticket from a pre-existing ticket, the child ticket either auto-filled the details from the existing ticket (perhaps a setting that can be toggled on or off?) OR displayed the existing ticket info at the top or in the side panel.
If not those features, at least make it so that clicking "Cancel" on the child ticket creation screen from an existing ticket takes you back to the existing ticket instead of the All Tickets screen.
When creating a child or parent ticket from within an existing ticket, I click "New child ticket," which opens the "New ticket" window. But I sometimes forget to check the site, user, priority, etc. before clicking "New child ticket" and the info isn't displayed anywhere in that new window.
If I click "Cancel" to go back to the existing ticket to copy the info, for some reason it doesn't take me back to the existing ticket I was just in. Instead it takes me to the default "All Tickets" page.
From there I have to find the existing ticket again,…
1 vote -
Deleting comments
Ability to delete comments.
If an external email has dropped inappropriate content into a ticket, we should be able to delete that ticket comment to remove the content.
47 votes -
Sort or filter by tag.
Being able to sort by Tag or filter all with out a particular tag.
1 vote -
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 -
agent detection intermitent and not able to connect
lately its been pretty bad the agent detection, atera simply is not able to detect computers anymore, even tho after updating the agent which was something bad as well, now very very often the computers just disappear from the panel impossible to connect , before everything was a breeze , not its hard., yo need to fix that , thats the core of your service or not?
4 votes -
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 -
Invoices list filtered by status
Please allow the ability to filter the "Invoices" list on the billing page by status. This will allow us to quickly find unsent or unpaid invoices versus loading page after page of invoices.
3 votes -
Popup Window Options
It would be excellent if the popup windows for AI Copilot and other functions (such as patch lists, etc.) were reworked so that you can see and use the AI tool.
2 votes
- Don't see your idea?