4812 results found
-
User ID in .csv download
We want to do a monthly download of assets as a backup to online inventory. In current .csv download 'user ID' column is blank even for those assets I have tied to a user. Can we add 'user name' to this .csv (or replace this useless column w it).
1 vote -
Ticket Form Filtering & Access Control
We need the ability to filter tickets by Ticket Form on the Tickets page, as well as display Ticket Form as a column.
We also need form-level user access/visibility controls, so administrators can choose which users or groups can see and use each ticket form.
Some forms are intended only for IT, such as incident or sanitization forms, while others are intended only for HR, such as onboarding and offboarding forms.
Having every ticket form visible to every user is confusing, cluttered, and impractical, especially as the number of forms grows.1 vote -
Start ticket timer when technician is assigned
I'd like a global rule that could start the ticket timer only after a technician has been assigned to a ticket.
In our setup, tickets flow into a technician group, then those techs manually assign the tickets to themselves. Having the ticket timer start when just viewing a ticket is making the feature not as useful.
We're also seeing the ticket timer still running even when there are no tickets opened in ticket tabs.
1 vote -
Devices automation
It would be helpful if agents could return more detailed hardware information, such as connected monitors and USB devices (external hard drives, printers, headsets, etc.). This would allow manufacturer names and serial numbers to sync with the asset inventory for better tracking.
It would also be useful for the agent to associate the device with the currently logged-in user. If the device is reassigned, the agent could identify the new user and update the information in Atera accordingly.
1 vote -
Native Endpoint Privilege Management (EPM), Just-in-Time Admin & Application Allowlisting
Atera would benefit greatly from a native Endpoint Control module similar to idemeum Endpoint Control.
The goal would be to combine Endpoint Privilege Management, Just-in-Time Admin Access and Application Allowlisting directly within the existing Atera Agent.
Key features could include:
Remove permanent local admin rights from users
Just-in-Time temporary admin access
Elevate individual applications without granting full admin rights
Technician approval/denial of elevation requests
Policy-based automatic elevation for trusted applications
Application Allowlisting / Default-Deny
Audit / learning mode before enforcement
Allow rules based on publisher, certificate, hash or path
User requests for blocked applications
Approval directly from the Atera console…1 vote -
Lightweight / Headless Linux Server Agent for Monitoring, Patching, Software Management and SSH
It would be very useful to have a lightweight, headless variant of the Atera Linux Agent that is specifically designed for Linux servers.
The current Linux agent covers many important management functions, but for server-only environments there is no need for desktop-oriented features or remote desktop components such as Splashtop, AnyDesk, or similar tools.
The idea would be to provide a minimal Linux Server Agent focused only on core server management functionality, such as:
System monitoring and alerting
CPU, memory, disk, network and service monitoring
Patch management
Package/software installation and management via APT, YUM/DNF, etc.
Script and command execution
SSH…1 vote -
Warranty expiration notification and alert
Configure and send a notification email or trigger an alert when the asset’s warranty is nearing expiration
1 vote -
Customer Remote Access Audit Portal / API
We would like a way to provide managed customers with read-only visibility of remote access sessions performed by our technicians on their devices, without granting them Full Admin access to Atera.
Ideally, this could be implemented through one or more of the following:
A customer-scoped Remote Access Audit report
Read-only access for customers to view remote sessions performed on their devices
An API endpoint for Audit Logs / Remote Sessions
Scheduled automatic exports or reports filtered by customer
The information should include at least:
Technician name
Customer
Device
Remote access method (Splashtop, AnyDesk, etc.)
Session start and end time
Session…1 vote -
New Ticket Reply Box (bottom)
Please consider restoring the ticket reply box to the top of the ticket view or adding a user preference to place it either at the top or bottom.
The current bottom-only placement creates challenges when working on smaller screens and mobile browsers. Users often need to review lengthy ticket histories and then scroll all the way to the bottom to enter a response. This negatively impacts efficiency and makes ticket management more cumbersome.
Allowing users to select their preferred reply box location would significantly improve usability and accessibility across different devices.
1 vote -
Ability to edit tickets
Please give admins ability to edit the tickets to remove duplicates, long emails that are forwarded, and mistakes.
2 votes -
having a piece of hardware not associated with a user
When tickets are created by a user, the system that is assigned to them is automatically picked. However there are problems with this setup. #1 Users can be using a different machine, say in a conference room that is the one that is having trouble. #2 The device in question is their CELL PHONE. Right now we have no way to tie a ticket to a device that isn't a computer, and we can only assign a device for the user that created the ticket. that is too restrictive.
1 vote -
liste client
Est-il possible d'exporter la liste des clients comme nous pouvons exporter la liste des appareils.
1 vote -
liste client
Est-il possible d'exporter la liste des clients comme nous pouvons exporter la liste des appareils.
1 vote -
Customer Exclusion List for Technicians
It would be great to have a feature that allows administrators to exclude specific customers from selected users or permission profiles.
A practical example: I would like to manage my company's internal devices through Atera and would like them to appear as a customer. I need full access as an administrator, but I do not want my technicians to view or manage those devices.
While customer assignments can currently be managed through permission profiles, this requires ongoing maintenance whenever new customers are added. A "deny access to this customer" option would be much simpler, require less maintenance, and ensure consistent…
1 vote -
Can we bring back the refresh button on the products page.
On the ticket > products, when you add a product you can't refresh the page to you have to exit all the way to the ticket and back again before the new product shows.
In the old UI, there was a refresh button to simple refresh all the products.This is yet another example of regression of the product. :(
1 vote -
Introduce a technician-side To-Do List feature
Introduce a technician-side To-Do List feature, to manage multi-activity tickets without exposing them as separate tickets in the Service Desk/customer portal
1 vote -
Improve visibility and management of Parent-Child ticket relationship in Service Desk
When a user opens a ticket from the user portal with a dedicated Onboarding/Offboarding form, only one ticket is created. Internally, child subtickets are created for each activity (Atera lacks a To Do list). The customer side will see many open tickets and won't know which is the parent ticket and which are the child tickets.
Consider:
* View Parent-Child relationship in the service desk
* Ability to filter only the parent ticket
* Create a To Do List on the technical side to manage tickets with multiple activities that are not visible to the Service Desk1 vote -
Field assignment on Child tickets created via automation rules after Parent ticket was created
We use one automation rule to create Child tickets (subtasks) when a parent ticket is created from another department ( example Onboarding/offboarding), and a second rule to assign a technician to each Child ticket.
The second rule never triggers, because Atera does not allow an action performed by one automation rule (creating a Child ticket) to act as a trigger for another rule. As a result, Child tickets are always empty and created without a technician assigned, requiring manual assignment every time.
Please consider:
* Allowing automation rules to trigger other automation rules, or
* Allowing technician or other fields…1 vote -
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
- Don't see your idea?