- or
No existing idea results
- ~ No ideas found ~
4807 results found
-
API key for specific customers
The new granular API keys are a great improvement and definitely a step in the right direction. One enhancement I’d like to suggest is the ability to restrict a key to specific customers when creating it. We use technician accounts that only have access to one or a few customers, and currently we can’t issue API keys to those users without unintentionally granting access to data beyond their assigned customers.
1 vote -
Save a ticket reply as an editable draft, unsent, for review before it goes to the end user
Atera offers exactly two states for a technician's ticket message: a public reply, which is immediately visible to the end user and sends an email, and an internal note, which is never sent. There is nothing in between — no way to compose a reply, save it unsent, and return to it later. The same gap exists in the API: CreateTicketCommentDTO carries no draft or status flag, and "draft" appears nowhere in the v3 specification.
The use case: a junior technician drafts an answer, the ticket owner or a senior colleague reviews and edits it, and only then does it go out. The same applies to a reply prepared by an automated or AI assistant that a human has to approve before it reaches the customer.
Proposed behaviour: a "Save as draft" action alongside Public reply and Internal note. The draft is stored on the ticket, visible and editable by any technician with access to that ticket, editable any number of times, and sent only when someone explicitly clicks Send. The same state should be exposed in the API, so integrations can create and update drafts.
An internal note is not a substitute. Per Atera's own ticketing documentation an internal note can never be edited or deleted once saved, so it is a permanent record rather than a working buffer, and it offers no path to being sent. The only workaround today is composing the reply outside Atera and pasting it in, which separates the text from the ticket context.
Atera offers exactly two states for a technician's ticket message: a public reply, which is immediately visible to the end user and sends an email, and an internal note, which is never sent. There is nothing in between — no way to compose a reply, save it unsent, and return to it later. The same gap exists in the API: CreateTicketCommentDTO carries no draft or status flag, and "draft" appears nowhere in the v3 specification.
The use case: a junior technician drafts an answer, the ticket owner or a senior colleague reviews and edits it, and only then does it…
1 vote -
Dynamic date filter for tickets
I would like to have a ticket filter that says "older than xy days"
We use a filter that says "older than 1 month", but I have to adjust it manually every month because that option does not exist.
1 vote -
Driver version - Hardware
It would be useful if, when selecting a device, a submenu was available within the Hardware section, in which to collect the different peripherals and display the list of drivers with their relative versions.
4 votes -
More "snippets" available
Beginning to use approval requests in tickets and would like to be able to list who the selected approvers are when sending out an email to let people know who is approving or denying their request. Expanding on that more available options to use as snippets when sending a form email would be helpful.
1 vote -
support proxmox host
a modifyed client that supports proxmox host, with all the standard proxmox services
1 vote -
New Patch automation page
It does not appear that the new format for creating/editing automation profiles is saving the email for notifications.
2 votes -
Notes field should be visible and searchable from the main devices page
It should be visible (selectable from Edit columns on Devices page) and searchable from the main devices page, so I can add something like the location (ex. Tom's Office) or who the user is and I can quickly find that computer based on my comment.
7 votes -
Stop changing the interface!
Sick and tired of the constant changes, and always for the worst it seems.
I now have to have the side bar pinned wide, or I get it flashing wide/small/wide/small as I work and move my mouse about.
Used to be able to select then copy the ticket number and title in one easy go.
Then a change and now I need to select it just right to get both, but when pasted it would be over two lines.
Then most recent change and selecting is still a pain but can acheive that, but now pasting is over three lines.
Get used to input on the top, and reading bottom to top.
Now the input is on the bottom, and read top to bottom, but ticket activity is still bottom to top.What really is the worst is the change of date/time.
Before I could copy date/time in one go from an entry, nice and easy.
Now the date is above outside of the entry, so I need to copy time, then type out date.
The time is not in 23hour format either.Change everything for changes sake, make it worse, yet no dark mode, still, after how many years?!
Sick and tired of the constant changes, and always for the worst it seems.
I now have to have the side bar pinned wide, or I get it flashing wide/small/wide/small as I work and move my mouse about.
Used to be able to select then copy the ticket number and title in one easy go.
Then a change and now I need to select it just right to get both, but when pasted it would be over two lines.
Then most recent change and selecting is still a pain but can acheive that, but now pasting is over three lines.
…
1 vote -
Slashtop Chatting
Have the option to chat with end users through SplashTop without having to remotely connect to their machines.
9 votes -
Please allow us to hide the copilot column on the lists (such as device list)
The co pilot column is clunky, cannot be dragged, and is frankly in the way. I would like to be able to opt out of it being there. Or could you at least downgrade it to be a drop down option for the row?
Anyways, both me and my co workers have been having problems with this and find the new UI generally clunky. This is one such reason.
1 vote -
newest
the ticket order newest to oldest i dont like at all
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 be checked and installed automatically at that interval even if the normal Windows Update Schedule is disabled. There are also options for scheduled day and times, but the interval setting should run independently of that.
Yes, we can create an IT automation profile to install definition updates daily or multiple times a day, but it clutters up the automation run history log.2) Exclude KB2267602 from the available patches indicators. (Or at least have an option to do so) . You could also add it as a separate definition updates indicator column that could be turned on.
3) Add the most recent definitions update version and date to the device OS and Security page
4) In addition to the all or nothing Windows Update settings in the Atera Configuration policies, let us pick an advanced option with all of the same knobs that are available in group policy: https://learn.microsoft.com/en-us/windows/deployment/update/waas-wu-settings
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 -
SLA Condition for ticket automation
Create a condition based on the SLA remaining - i.e. SLA remaining is 2 hours, then we can configure an action such as sending an email based on that SLA. Currently to do this, we have to use your BETA Hours since created ticket, but this doesn't work well with dynamic SLA times.
2 votes -
Snooze indefinitely on Alerts
Snooze indefinitely on Alerts, the maximum is currently monthly, but indefinitely would help as an option where service are no longer in use on servers, etc., but are being flagged by the associated threshold configuration
3 votes -
Veeam 365 Backup including Public Folders
Veeam 365 Backup includes Public Folders, cannot find anyone else offering this.
1 vote -
Make ticket timer go away when creating ticket
We are not an MSP and I don't lord over my tech with how long things take and how long it takes to open a damn ticket. I absolutely hate the ticket timer. I DO have it hidden, but it still shows up when I create a ticket and it's checked by default. Give us power to get rid of this nasty thing. Thank you!
2 votes -
Adding the option to append the date of the ticket creation to the ticket number.
We are in the process of onboarding with Atera and noticed that the ticket numbers are simply an incrementing number.
Some of our users appreciated the old system's ticket numbers including the date that it was created. an example being 15-11202025, this way it can be identified as the 15th ticket created on 11/20/2025.
Can a checkbox option be added in the settings for companies to choose to add the date to their ticket numbers?
6 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 -
Need Ability to Add Private IP & Notes in Devices View
The devices view is too limited on what columns you can include. We need at minimum the Private IP & Notes and maybe even a column for warranty expiration. We can get this from reports but we work from the Devices view most often and it's very limiting and causes extra clicks when not necessary because we can only add select columns to a view.
2 votes
- Don't see your idea?