215 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.
22 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.
12 votes -
ticket automation out of hours response
In the ticket automation should be able to send an auto reply if the ticket arrives out of hours, this way we can direct them appropriately.
Therefore we need a way to trigger the ticket depending on the time of day it arrives.
2 votes -
when resorting cols in the ticket they need to stay how i set them
The new ui for tickets doesn't fit on a single screen and the order they put the data cols in is useless (who cares about sentiment its a joke) when I reorder or remove COLS from the ticket screen the changes should persist instead of resetting every time page reloads. I need to have it so statuses of the ticket are FIRST .
3 votes -
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 -
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 -
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 -
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 -
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 -
Date format API
The date format should generally be configurable, and in communication with the API, it should at least conform to ISO 8061
3 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 -
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.
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
- Don't see your idea?