4798 results found
-
Ticket Timer Automation rule
Please allow me to trigger with Automation rules the ticket timer, the automatically start timer on ticket open is not an accurate way to track time. My Goal is to set automation flows that automatically start and pause the timer based upon my ticket status.
11 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. You are also welcome to review the most recent comment added from our Product Marketing Team.
http://atera.uservoice.com/forums/936306/suggestions/50683820
Best regards,
The Atera Team
-
Improve adding Manual Time Entries
In the new UI, entering manual time entries is very laborious.
Having to enter HH:MM:SS and then type AM or PM, twice (start and finish) multiple times per day is very annoying.
It should be in 24-hour format. So we just enter, for example, 11.48 and 13.17, and that’s it. If we don’t enter seconds then these should default to 00 on seconds.
228 votes -
1st time fix report
I would like to know in a percentage how many of my issues are fixed on a 1st time basis.
1 vote -
Remove deactivated users from site lists
After a user leaves, I don't want to still see them in the site lists. Need a way to manage that or the site lists will get bloated with termed employees.
1 vote -
Feature Requests: Automated Reply Sender Address & Dashboard Customization by Technician Group
Hi Atera Team,
Following up on our recent chat with Constantin (Aug 27), we'd like to formally submit two feature requests, as we understand these aren't currently supported but would significantly improve our workflow.
- Automatic Reply Sender Address per Technician Group
We have multiple Support Addresses set up (e.g., knowledge@inc.com for our Knowledge Team, support@.global for Helpdesk Support), each tied to its own Ticket Automation Rule and Email Template.
Currently, when a ticket is generated via a specific address (e.g., knowledge@inc.com), the automatic reply is still sent from the default outgoing address (support@.global), regardless of which…
1 vote -
Add Online/Offline Status to the Software Inventory Report
Please add a device availability status field to the Software Inventory report.
The report should include an additional column showing whether each computer is currently:
Online
OfflineThe status should also be included when exporting or scheduling the report in Excel, CSV, or PDF format.
This would make it possible to distinguish software inventory data received from currently connected computers from cached inventory data belonging to offline computers.
It would also be useful to add the following fields:
Last Seen
Availability Monitoring Enabled/Disabled
Folder
Device TypePlease make these fields available both in the built-in Software Inventory report and in…
1 vote -
Allow Custom Reboot Schedule Times (Not Limited to 30-Minute Intervals)
Currently, reboot schedules can only be configured in 30-minute increments. Please allow administrators to manually specify an exact reboot time (e.g., 10:15 PM, 11:05 PM, etc.). This would provide greater flexibility for maintenance windows, patching schedules, and minimizing user impact.
1 vote -
Make API feature complete
Time and time again we realized that we cannot automate certain Atera features via API from our agents (AI agents..). I think the time has come that companies need to provide a feature-complete API and not put things behind their UI or their own agents so that we buy their extended packages.
A feature incomplete API is a bug, not a missing feature..
Here some examples we cannot do via API that are possible via UI:
- Run a script or command on an agent
- Assign or remove an automation profile
- List, assign or change a threshold profile
- See which automation,…
1 vote -
Approval Automation for Ticket Form Templates and Automation Features
It would be great if the ticket form templates could have a built-in automation workflow. Ideally, if someone fills out a template it will add users to approve it and then assign it to a technician. Right now, approvals have to be manually added to tickets.
Additionally, there should be more ticket automation actions where triggers can assign tickets to users.
3 votes -
Status Selection on Ticket Creation (Dashboard)
Feature Request
Add a Status dropdown field to the ticket creation form in the Atera RMM dashboard, allowing the technician to set an initial status at the time of ticket creation rather than defaulting all new tickets to "Open."Current Behavior
All tickets created from the dashboard default to "Open" regardless of context. There is no way to set the status during creation — it must be changed as a second step after the ticket is saved.Requested Behavior
When creating a ticket from the dashboard, the technician should be able to select a status from a dropdown at creation…2 votes -
Default Remote Access Option (No Warning)
The Default Remote Access Option allows one to change from Splashtop to AnyDesk/TeamViewer/ScreenConnect.
The problem is, an admin can change this without warning. It provides no warning or confirmation or context. It immediately just deploys AnyDesk etc. to all agents causing popups on Macbooks and security alerts and mass panic.
Please can you consider a warning confirmation dialogue before this setting is changed or updated? Should be a quick small change hopefully.
29 votes -
Allow managing multiple hardware-bound / device-specific Passkeys per technician account
Currently, Atera only triggers the passkey creation prompt once during setup. If a technician registers a hardware-bound passkey (e.g., local Windows Hello / TPM module), it is impossible to register a second device (like a secondary workstation or laptop) without completely resetting 2FA for the account. Resetting 2FA invalidates all previously configured credentials, making it impossible to use multiple hardware-bound keys simultaneously.
Technicians are currently forced to use cloud-synced passkey managers (like Chrome or iCloud Keychain), which is not compliant with many enterprise security environments that strictly mandate hardware-bound TPM credentials or physical FIDO2 tokens.
1 vote -
Logout and lock user accounts from Atera
The ability to force the logout of a user session & lock user accounts from the Atera portal. I am currently doing this with scripts however, unless the user is currently signed in, it can be difficult for the scripts to identify the owner's account etc.
1 vote -
New Tickets page UI - Feedback [Q1, 2026 Feature release]
Hi everyone — we’d love feedback on the new Tickets page UI (the redesigned, configurable table).
What’s new (vs old Tickets page):
- Detailed vs Compact view (Compact = more rows per screen)
- Show/hide columns
- Reorder columns
- Sorting + saved views
- New columns: Approval status, Created date, Last action date, Parent/Child tickets
What we need from you:
- Reply with anything you’ve noticed, but if you can, use this quick format:
1) Your setup
- Detailed or Compact?
- High-volume queue or occasional triage?2) What works
- What’s better than the old page?
- Missing columns?
- Too many clicks?…3 votes -
API Enhancement: Add 'LastInternalComment' and 'IsSolution' Properties
We request two specific additions to the API to improve ticket management and documentation:
Ticket Endpoint: Add a LastInternalComment field (similar to the existing LastEndUserComment).
Comments Endpoint: In GET /api/v3/tickets/{ticketId}/comments, include the boolean status IsSolution for each comment object.
Context & Why this is useful:
LastInternalComment: We need to quickly see the status of a ticket based on the last technician note, not just the user's reply. Currently, we have to download all comments to find the last internal update.
IsSolution: When syncing tickets to a knowledge base or sending final reports to customers, we need to programmatically identify which…
6 votes -
Access Roles hide/restrict
Subject: Feature Request – Access Roles should hide menu items/widgets based on permissions
When I disable a permission (e.g., Patch-Management → "View and install patches directly on devices") for an Access Role, the Patch-Management menu item still appears in the left sidebar for that user, even though they have no access to it.
Request:
The left navigation menu should dynamically show/hide items based on the permissions granted to the user's Access Role. If no permissions are enabled for a module, the menu item should be hidden entirely — not shown as an inaccessible/disabled entry.
This would allow admins to create…1 vote -
add a script to the IT Automation profile
There's no API to push scripts to the IT Automation and Patch Management dashboard. Having that will simplify script management and deployment.
1 vote -
Windows Toast Notifications with Automation Progress
Add an option to display an interactive Windows Toast notification on the end-user device when a script or automation profile is being executed.
We’d like to have a simple tick box/checkbox that can be enabled when deploying a script or automation profile, allowing Atera to display a Windows Toast notification to the user on the affected device.
Suggested functionality
When enabled, the user would see a Windows notification such as:
IT Helpdesk (or Atera) Automation in Progress
An automated task is currently running on your device.Progress: 65%
█████████████░░░░░░Current task: Installing Windows Updates
The notification could dynamically update as…
1 vote -
Per-Customer breakdown of subscription costs
Atera supports multiple customers. That's why we use it.
Different subscriptions are applied to different customers. But some subscriptions are applied to multiple customers.
Whoever uses Atera gets a bill, and with some digging, can find the breakdown of the monthly cost of each subscription... but we bill customers based on their part of the subscription. The bill we get only shows a total cost. I can see X total seats in use, but not X seats for customer A, Y seats for customer B, Z seats for customer C, etc.
It would be extremely helpful--necessary, actually--to see a per-customer…
1 vote -
Copilot has only been effective approx 35-40% of the time. I am forced to continue prompts, lead it towards a solution. Waste of time.
Copilot Developer feedback list: 1) Give the AI secure, read‑only access to ticket‑linked mailboxes, 2) Add URL sandbox/reputation checks for every link in a message, 3) Expose more endpoint automations so fewer answers fall back to “manual,” 4) Reduce tool‑call overhead so technicians get direct actions, not workflows, 5) Improve accuracy/coverage so the assistant is useful >90% of the time, 6) Make limitations explicit in‑product so techs don’t waste time discovering them.
1 vote
- Don't see your idea?