209 results found
-
New look menu is a step backwards
The new menu interface has hidden 'Knowledge base' behind a 'More' button but left items we never use. we need the option to pin or rearrange menu items.
9 votes -
Advertisements
Please, Please stop all of this stupid advertising. We are here to work not worry about where we click . AI crap is always in the way, at login always advertising . Stop, Just Stop.
3 votes -
Dark Mode for Web app and iOS
Are there plans for native dark mode for both the iOS app and web interface?
As IT professionals who staring at screens all day, this would help reduce eye strain day to day and align Atera with modern tools that already support dark mode.
Ideally:
iOS could follow system dark mode
Web could include a simple toggle or follow the system default
This would be a great quality-of-life improvement for daily use.2 votes -
Improve Handling of Security intelligence updates (KB2267602)
Currently the Windows Update setting in the Atera Configuration policies are to allow local updates or disable all local settings. The problem with the latter option is that it also disables the automatic updating of Security intelligence updates (KB2267602). Every device will perpetually show as needing that update since Microsoft re-releases it multiple times a day. More info here: https://www.microsoft.com/en-us/wdsi/defenderupdates
I propose the following:
1) Add configuration options under the Atera Configuration Profiles for the Security Intelligence Updates. The most important one can be set with this PowerShell command: "Set-MpPreference -SignatureUpdateInterval <hours>". By setting this, updates for KB2267602 should automatically…4 votes -
Change Main Site Contact or Certain user permissions to view all tickets.
We need the ability to change Main Site Contact or allow certain users to be able to see all tickets.
Currently for certain users to see all tickets they need to be marked as a "Main User" but this can also make them a "Main Site Contact". If tickets come from Atera Alerts this will use the "Main Site Contact" to email from, generating tickets by that user who was last assigned as a "Main User" rather than a generic ITsupport user account instead.
6 votes -
Granular permissions for Access Roles
There should be more granular control to allow certain roles to be able to view ticket. As it currently stands, the only ticket options are Access all assigned tickets or Access unassigned tickets. I would like to see the ability to be able to select what tickets a role can see. This would help supervisors be able to only see their department.
2 votes -
Implement domain-based restrictions for automatic contact creation from incoming ticket emails.
Implement domain-based restrictions for automatic contact creation from incoming ticket emails.
Currently, the setting applies to either all or none.For example:
- Do not create contacts for emails originating from public domains (e.g., Gmail).
- Automatically create contacts for emails from recognized company domains.Ideas for configuation either:
- Maintaining an allow list of approved domains, or
- Maintaining a block list of domains to exclude from contact creation.
Thank you for your consideration
1 vote -
Device Info History - Hostname, Logins, Reboots
There are many ideas like this one, but they are limited to very specific things - most of them targeting the user history.
We need more than just user history, we need ALL history. Most things on the Overview page should have their own history tracking. Sure, things might be tracked in the activity log - but sometimes we need very specific information that may not be logged at all.
First and foremost, every one of these fields should have a little icon next to them to display the history of the field. You will also note I have included…
6 votes -
Contacts should include a Department Field
We have clients that require us to bill by Department. It would be great if the Contacts screen had an additional field, that displays right under the the Cusomer Name, "Department", so it is viewable on on the Ticket details screen in the Contact info area.
4 votes -
Email notifications on Public notes when CCd
Currently no email notification is sent to a technician when they are mentioned in a Public note, this to me sounds like a simple request and is causing members of our team to miss ticket notes that they have been tagged in
1 vote -
Customer creation for level 1 techncians
We need non-admin users to be able to create Customers. We have custom roles created, and a lower level technician should be able to create a new customer, assign contacts and set them up. Deletion (or even better - archive, deactivate, or retire a customer) should certainly fall to an Admin role.
1 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 -
Date format API
The date format should generally be configurable, and in communication with the API, it should at least conform to ISO 8061
2 votes -
Folders/Organization for Ticket Automations and Patch Automations
We have a lot of ticket automations and patch management automations set up as every customer needs things set up a little different. Over time, this adds up and makes the automation pages feel very cluttered. It would be nice to have a way to organize these, ideally by customer. For ticket automations in particular, if it's broken down by customer, the ticket automations would only run for that customer. So, you could have general ticket automations and customer-specific ticket automations.
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 -
Wildcards in searches
"While the global search has been enhanced to be a fuzzy search, and also now includes custom fields, searches in general are still missing proper wildcards.
First and foremost, I would like to see the common '' and '?' wildcards honored. Even the advanced filters lack this ability, only providing the 'contains' which is just a poor man's wildcard providing the basic '<search>*' option.
Bonus points if you will implement a RegEx function in some way... whether it is a checkbox next to the search box or initiated by some special character combination, such capabilities deserve to be…
1 vote -
Set roles that can use outbound support email addresses rather than customers
It would be incredibly useful to be able to select what technician groups/individual technicians can use what outbound email address.
I.E. IT Support Technician uses helpdesk@, Security Technician uses security@
Rather than it just being limited to what customers can receive from what outbound email address.
As an example, we have multiple departments that handle tickets and each has its own mail address so we can manage the flow of tickets as they come in. I don't want my IT team address being used for Security tickets, comms tickets, project tickets etc. I want to be able to define what…
1 vote -
contacts
BUG: Deactivated Contacts are Visible by Default
Deactivated contacts are still visible by default. Deactivated contacts should be filtered out by default. If people want to see the deactivated contacts, they should be able to turn that filter item on in the filter settings.
3 votes -
scheduled script
I want to be able to choose the exact day and time my scripts run on customer computers. Not every task fits into fixed repeating schedules. Customers have different routines, time zones, and specific needs.
1 vote -
Mac Modell Specification
Mac Specification
In the device overview, it would be helpful to be able to differentiate which Apple model is being displayed under the Hardware tab, instead of just seeing "Mac" next to the model name. This would be extremely useful for sharing information with documentation systems.
1 vote
- Don't see your idea?