4702 results found
-
Asset autofill from devices found in network discovery and in the device list
When I view a device in Atera - I can see the make, model, SN, OS, and a slew of other important information. It would be very beneficial if I could press a button and tell it to convert to asset - this would save a TON of time - and it would prevent me from having to double up on my data entry.
2 votes -
It would be very helpful to be able to create schedules for alert suppression on devices.
Currently we only have the option to manually suppress alerts at the device level for between one and five hours, and we cannot schedule this for future times. It would be VERY helpful to us and to our clients to be able to create maintenance schedules where devices will automatically go into and out of maintenance mode. Often our client will ask us to suppress alerts for certain time frames starting on certain days, and it's impossible to do this with the current solution. Thank you.
2 votes -
Create device folders based on reports/multiple folder assignments
I would be great to have the ability to create a folder containing all devices within a report. There are times where a folder is needed to easily run scripts, set policies, etc. It would also be beneficial to assign devices multiple folders/groups for this reason.
2 votes -
View "Date Modified" for File Transfer Window
I would be helpful to view the date modified for files on endpoints using the file transfer feature.
2 votes -
Using splashtop to external agents/users
We need to use splashtop not only for our domain and registered to atera users but also to our external on their own devices.
How is this possible ?
2 votes -
More customizable dashboard
The dashboard should be able to more customizable, not just have checkboxes for predetermined widgets. Should be able to add any view already in Atera, such as device views, ticket views, etc. So you could also have a ticket widget that is a breakdown per customer, devices per customer, devices in a patched, not patched status etc.
16 votes -
export tickets specifically with comments left alongside ratings
export tickets where users have left a rating along with a comment, so we can specifically see what they were satisfied or dissatisfied with
1 vote -
Show active Network adapter
It would be great to see under the hardware heading which network adapter is currently active and what the in/out metrics are. Our remote users are instructed to use the ethernet cable we provide but some try to get away with using their wifi connection, which is not robust or reliable enough for our proprietary software.
2 votes -
shortcut
Customize the default shortcut Ctrl + F12 to post a ticket
2 votes -
Intune
Provide a UWP app for Intune AutoPilot for MDM and deployments over the cloud.
16 votes -
Lineup tickets / requestor advise
When a "requestor" adds a ticket in the system, it is quite very helpful to be advised by the number of already opened tickets in the system , so he/she will know how many cases the technicians have to deal with before start working to theirs.
1 vote -
Generic or branded agent name
Agent should be generic name or allow branding
White Label branding is in nearly all competitors products to allow branding! Atera should also allow customizing and branding or generically displaying the install program name and folder name, as well as in the Apps and Add Remove Program Files.
Instead of “Atera” under Program Files or Program Files (x86), or the Apps and Add Remove Program files use something like "ITSupportAgent" or “CompanyNameSupport” Customers see the Atera program and do not know it and uninstall it. If it was the IT department or service providers name they would recognize it.
Branding…
14 votes -
Text box drag to enlarge
I don't like how the text box, when typing notes/replies, has to either be Fullscreen or letterbox style.
I just want to be able to drag the text box to make it longer, rather than have to bounce in and out of Fullscreen.
2 votes -
Asign multiple roles to a technician
In case of IT support teams spread on multiple sites (e.g. Technician A has an admin role for Site A, technician B has an admin role for Site B) as a supervisor for all sites and resident on site C, I would like to be able to assign tickets (or change requests) to technicians without having to make them admins of site C.
In summary: the ability to assign multiple roles to the same techincian or be able to differentiate ACL for each site within a single role5 votes -
Chrome OS
The ability to install RMM software on Chromebooks and other ChromeOS devices.
27 votes -
Permission option to close other tech ticket
Currently there is a permission option to view other technician ticket but there should be an additional permission (on and off) for a technician ability to close tickets that don't belong to them.
SLA, time entry and CSAT are linked with ticket owner and tech should not have the ability to close ticket on behalf of another technician. Only team leader or Admin should have this ability. We want all our tech to view all tickets, as when a customer calls and if the tech is not available, they can provide update to client. But technician should be restricted from…5 votes -
2 votes
-
System to handle email notifications to copied recipients on tickets, not rely on "Reply All" from email client
No notification sent to copied parties on ticket if primary customer does not use "Reply All" when they respond to a ticket via email or if they delete email recipients from email response.
You cannot rely on the customer to click on "Rely All", if you do and there is another party that needs to be included for example an escalation with their manager or a "cover your butt side", they will not receive the communication reply to the ticket.
I have had a recent incident whereby the primary removed their manager from the "Reply All" email, so it wasn't…
1 vote -
App sign in
Sign in with Mobile app. Also Multiple fingers for authentication.
3 votes -
Approval for knowledgebase
Have the ability to set approval workflow for articles in knowledge base. Suggested status would be: "For approval", "Approved", "Rejected".
"For approval" and "Rejected" shouldn't be visible in customer knowledge base in customer portal, but "For approval" should be visible in internal knowledge base in Atera, for selected roles. Admin-roles should be able to see everything in Atera.Also be able to set who can approve and who can submit for approval, lets say for internal knowledge base Tier 1 technician can only submit, but admin can approve and reject. For customer knowledge base selected customer end user (preferably IT-manager)…
5 votes
- Don't see your idea?