- or
No existing idea results
- ~ No ideas found ~
5041 results found
-
Spell Check
Adding spell check when replying to a ticket
2 votes -
Automatic logout after time of inactivity
Automatic logout of a technician from the Atera console after a certain period of inactivity. For example, if a technician logs into the console on a computer at the customer's site and forgets to log out, the worst case scenario could be that the customer has access to all customers and their devices. Or even worse, can also access these devices. Certainly very questionable from a data protection point of view. At the moment, there is probably a timeout only after 72 hours. Or when he logs into the company again. But I find this very dangerous.
4 votes -
Ability to run a simple customer list that shows custom fields, i.e. assigned technician
It seems like such a simple thing but we need to be able to run a customer list report. We would also need to include or filter by any added custom fields to the record.
1 vote -
Disable the chat for multiple devices
Disable the chat for multiple devices
1 vote -
Stop certain tickets from being reopened
The ability to have a status such as "Block ticket" which will prevent the ticket being re-opened. This would be very useful for people who like to include the help desk in random email threads that are not support requests. I felt like this could have been easily achievable through ticket automation, however it doesn't appear to work and Atera support have advised this is not possible.
1 vote -
Improve Quick Reply Templates
Disabling the text "Comment here..." because when I choose a Quick Reply Template "BEFORE" I clicked once into the text box, this text is still under my templates text.
A global setting for a default template would be very useful because it makes replying much faster without all the time choosing a template before begin writing. =)
Please improve the template editor in case of usability, fonts etc. pp. Sometimes it looks like that the formatting isnt really accurate and changes from template to template.
Thanks a lot. =)
5 votes -
Assign Multiple Contacts for a single Device
Our organization has shared PCs where one device can have multiple contacts. As of right now, Atera only provides the ability to assign a single contact to a device. By allowing multiple contacts to be assigned, it can make it easier when users submit tickets to already know which device they belong to.
26 votes -
Allow ticket Creation when the send-to address is in the BCC Line
Currently Automatic ticket creation https://support.atera.com/hc/en-us/articles/360012444033-Forward-Email-for-Automatic-Ticket-Creation-in-Atera does NOT happen if the @ticketing.atera.com address is on the BCC line of the email. Sure, it works fine on TO: and CC: but if you want to sneak in a ticket on your reply email by BCC'ing the forwarding email, it will just get black-holed by Atera, and no ticket will be created.
2 votes -
Use single browser tab for Screenconnect sessions.
Use single/existing browser tab when launching Screenconnect remote session. Currently a new browser tab is created each time "Connect" is clicked.
8 votes -
Knowledge Base Import
Similar to how you can import Customers from a CSV, allow for efficient creation of Categories and Sections by using a template CSV.
9 votes -
FedRAMP Validation
It would be great for Atera to achieve FedRAMP validation for companies that are under NIST 800-171/CMMC compliance regulations.
3 votes -
Reports on internal notes
Reports on internal notes added to Atera by all or selected technicians for specific period of time.
3 votes -
Configuration Policy for installed software, settings
Assign a baseline policy for what software and settings should be applied and auto correct/reinstall if a change is detected. Similar to SCCM baseline configuration.
1 vote -
Ability to see missing Patches on offline device
Ability to see missing Patches on offline device
7 votes -
Block software downloads
Block software downloads on computers
7 votes -
Optimized Automation and Patch
Need to find a better solution for patch and automation.
The fact that you can't run Updates, System Restore Point, and a Restart all on one profile without it running into conflicts makes little sense to me.I have now made 9 total profiles (3 sets of 3 [we have 3 different types of patch profiles running at different intervals]) to fix this. For each type we have to run System restore point, then 1 hour later a separate schedule for patches, then 2 hours after that a different, separate profile for restart. Hopefully it works.
While it isn’t really TOO MUCH trouble, I would like to point out that from a programming standpoint, it seems like these items should have maybe a priority listing (If system restore is enabled, set item to #1 priority, pause any other scripting until item is finished, move on to next task, etc.), and while I understand that EVERY computer is different, there could be an estimated time frame to run the task listed next to the item.
So, it could be System restore is prioritized to number 1, then patch as 2, then restart as 3. You could maybe even have an option for us to change the priority levels ourselves. That being said, and the time frame being mentioned, it could list time frame for all checked boxes, and offer an estimated time for the whole profile to run. Just an idea, but I will say that needing to make 3 separate profiles to make sure these run in the correct orders, and times, makes this a bit tedious and frustrating to manage.
As I had said, it was not too much trouble, but the fact that I needed to take extra steps could be possibly avoided in the future for myself and other customers. I’m sure I’m not the first one to complain about this.
Thank you for your help, and sorry for the rant, but I just feel like there is possibly a better way.
Need to find a better solution for patch and automation.
The fact that you can't run Updates, System Restore Point, and a Restart all on one profile without it running into conflicts makes little sense to me.I have now made 9 total profiles (3 sets of 3 [we have 3 different types of patch profiles running at different intervals]) to fix this. For each type we have to run System restore point, then 1 hour later a separate schedule for patches, then 2 hours after that a different, separate profile for restart. Hopefully it works.
While it isn’t really…
32 votes -
Check customers domain for proper configuration of SPF/DKIM/DMARC
Monitor Proper Configuration on SPF/DKIM/DMARC and create a trouble ticket if something isn't right
6 votes -
Better organization for Attachments on Tickets
It would be nice to have an attachments tab or category on tickets. Somewhere where all the attachments on a particular ticket are viewable. Either similar to the attachment tab for customers or just linked to side like the other ticket details.
With the current system, it very easy to loose track of attachments, especially if someone else added it to the ticket because you may not see it without scrolling through all of the notes.
2 votes -
Give Macintosh models better descriptions
Currently in the Atera web dashboard, if you view a Mac device, under Hardware->Device it only lists a basic description of Mac ("iMac" or "MacBook Pro"). This same description is given on the Mobile app, under Hardware->Motherboard. It would be more informative if Atera at least displayed the Model identifier in these locations, as the result from "/usr/sbin/sysctl -n hw.model" gives "MacBookPro18,3". Ideally, Atera would use the result from the Apple Marketing Name instead ("MacBook Pro, (14-inch, 2021)"), but there isn't a consistent programatic method I've seen to grab the name. If we wanted that, best bet would be for Atera to build a lookup table server-side to convert model ID to marketing name and put the marketing name in the field (and the model ID if the entry isn't in the lookup table.) Apple provides the information necessary to build the complete lookup table for all models from at least the last 13 years on their support site; search for "Identify your mac model" to find the appropriate support documents.
Currently in the Atera web dashboard, if you view a Mac device, under Hardware->Device it only lists a basic description of Mac ("iMac" or "MacBook Pro"). This same description is given on the Mobile app, under Hardware->Motherboard. It would be more informative if Atera at least displayed the Model identifier in these locations, as the result from "/usr/sbin/sysctl -n hw.model" gives "MacBookPro18,3". Ideally, Atera would use the result from the Apple Marketing Name instead ("MacBook Pro, (14-inch, 2021)"), but there isn't a consistent programatic method I've seen to grab the name. If we wanted that, best bet would be for…
4 votes -
Adding Notes - Documentation
Bigger space to add notes for proper documentation.
97 votesCongratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
- Don't see your idea?