- or
No existing idea results
- ~ No ideas found ~
4800 results found
-
Ability to filter the run of IT automation and threshold profiles by agent details
If we create an IT automation or threshold profile that's only for Windows Servers then we have to create Profile at each and customer assign every Server to it and then assign every of that Server profiles to the automation profile
That's cumbersome and prone to errors
Much more efficient would be a set of filters at the automation profile, like "is Server" or "is a domain controller" or maony other smart things.
We would just assign am automation oder threshold profile to customers and it runs only at the matching agents
1 vote -
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 -
profil assignment for monitoring, patch management, automation could be more clear
to assigng a profile to a customer or to a , you have to drop down a customer (and a folder) and add ist.
Below you can see the allready assigned.What you can't see are the unassigned.
So you have to drop down an try to see, whats not assigned.
You will miss some.A (expanpandible for Customer-Folder) List of Checkboxes would be much more clear
1 vote -
Time entry billable round
Currently, if a ticket has a time entry duration of 1h:15m, the billable hours are set to 2 hours (Atera always rounds up).
It would be convenient if there was the option to round to 2 hours only if the work exceeds 1.5 hours (1h:30m).
For example: I work 1h:25m, the charge is 1 hour; if I work 1h:40m, the charge is 2 hours.Symply change the "Ticket Rounding" section in "Ticket Settings" to:
-None
-Quarter-hour
-Half-hour
-Hour (rounded mathematically) <<---new feature
-Hour (rounded up) <<--old feature renamed1 vote -
Display local activities in the activity log
Display local activities in the activity log
It would be helpful if the activity log for devices listed not only the actions performed on the Atera itself, but also those performed locally on the device. Many competitors already offer this feature. This would significantly simplify the workflow.
2 votes -
API Contacts (MSP)
API, GET contacts
add CustomerID filter option (obtain contacts for a specific customer)add Sync Source information (Entra = True)) into Contact data,
add also to GET /api/v3/contacts/{contactId}1 vote -
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 -
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
38 votes -
Event Log Triggers show Rule Title
When an alert is triggered I could care less to see the event. I want to see the title of the rule. That is the only thing that means anything to me. I can always look at the event log in the detail. THis is a major pain point as I either need to keep a list handy or click on each one to see what the issue actually is. Very annoying.
1 vote -
Favorite link at top of screen
Please place a favorite drop down at the top of the screen. I am constantly navigating to the same places. We should be able to tag any page, report, etc.
1 vote -
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 -
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 -
Ubiquiti Integration
Ubiquiti Integration
967 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
-
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
- Don't see your idea?