205 results found

1. Revamped Notification Center: real-time, user-specific notifications with history, CTAs

   Today’s Notification Center doesn’t reliably support real-time workflows: notifications aren’t consistently user-scoped, history is limited, and many messages don’t include clear next actions—making it harder to respond quickly and confidently. This idea proposes rebuilding Notifications on a modern, cross-domain infrastructure that supports async process updates (patching, scripts, deployments), plus AI-triggered notifications from Copilot and Autopilot, with full history and actionable CTAs.

   What we want to add (Multiple stages):

   • User-specific notifications (permission-aware): only see what you’re authorized to see; eliminate “tenant-wide noise.”
   • Real-time delivery + full history: a central hub to review past notifications (with retention, search, and filters). This aligns with repeated requests for notification history and richer desktop/browser notifications.
   • Actionable CTAs on every notification: “View ticket,” “Open device,” “Retry,” “Approve,” “See results,” “Authenticate,” etc.
   • Async process updates: patch run started/completed/failed, script queued/running/completed, bulk actions results, integration auth success/fail, exports, imports, report scheduling, etc. (Atera already supports alert email/sound and mobile alert push—this extends the model to broader workflows).
   • AI-triggered notifications: AI Copilot and IT Autopilot events (escalations, approvals needed, user authentication required, high-confidence resolutions, critical automation outcomes).
   • Prioritization + control: severity levels, grouping/deduping, mute/snooze rules, and per-user preferences (channels + types).

   Today’s Notification Center doesn’t reliably support real-time workflows: notifications aren’t consistently user-scoped, history is limited, and many messages don’t include clear next actions—making it harder to respond quickly and confidently. This idea proposes rebuilding Notifications on a modern, cross-domain infrastructure that supports async process updates (patching, scripts, deployments), plus AI-triggered notifications from Copilot and Autopilot, with full history and actionable CTAs.

   What we want to add (Multiple stages):

   • User-specific notifications (permission-aware): only see what you’re authorized to see; eliminate “tenant-wide noise.”
   • Real-time delivery + full history: a central hub to review past notifications (with retention, search, and filters). This aligns… more
   67 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   13 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. 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.

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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 an additional field, called 'Device hostname', because the simple fact is you can change the name of a device in Atera completely different than the hostname of the device... but both are important, and thus should not be ambiguous.

   Device name
   Device hostname
   Domain
   Public IP
   Last login
   Last reboot

   Furthermore, it would be good to see the history for the owner info:

   Customer
   Folder
   Contact

   Anytime a new field is added here, it should also be considered for history tracking. Perhaps there should be a limit on things like 'Public IP' and 'Last reboot' history, but that can easily be an internal setting in the admin console or set to a number that nobody would have a problem with, like 30.

   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… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Admin & Core platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 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 available in the main UI instead of the just the advanced reporting system."

   "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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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 team can use what outbound support address - this functionality exists in Halo and Autotask (our previous platform)

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Atera ipv6 Support for Agents

    Currently Atera lacks ipv6 support for agent installation and communication.

    The installer goes to <account>.servicedesk.atera.com which only resolves IPv4 IPs for servicedesk-us.southcentralus.cloudapp.azure.com.

    IPV6 support for other URLs:
    pubsub.atera.com - No
    pubsub.pubnub.com - No
    app.atera.com - Yes
    agenthb.atera.com - No
    packagesstore.blob.core.windows.net - No
    ps.pndsn.com - No
    agent-api.atera.com - No
    cacerts.thawte.com - No
    agentreportingstore.blob.core.windows.net - No
    atera-agent-heartbeat.servicebus.windows.net - No
    ps.atera.com - Yes
    atera.pubnubapi.com - No
    appcdn.atera.com - Yes
    atera-agent-heartbeat-cus.servicebus.windows.net - No
    ticketingitemsstoreeu.blob.core.windows.net - No
    download.visualstudio.microsoft.com - Yes
    a32dl55qcodech-ats.iot.eu-west-1.amazonaws.com - Yes

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. 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.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Solicitud de cambio de traducción de "Novedad" por "Nuevo" en la pantalla principal de Tickets

    Quisiera solicitar que el término "Novedad", que aparece como menú desplegable en la pantalla principal de Tickets (adjunto captura), sea reemplazado por "Nuevo" para mejorar la comprensión de los usuarios en español. El término "Nuevo" es más intuitivo y se ajusta mejor al contexto de creación de tickets.

    Adjunto imagen para referencia. ¡Gracias por considerar esta mejora!

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Automation

    I’d like the ability to use adding a contact to a customer to send an email based on a template with a link to install the Atera agent

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. kill this website

    This website is all but ignored by the dev team. just kill it so we do not get false hope.

    the dark mode request is a fiasco and honestly I give up. when my renewal comes due, I may just go elsewhere

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Prevent deletion with group permissions

    Add the option to prevent the deletion of an agent for a specific group.
    ES: Group A, flag to enable or disable the option to delete an agent from the web interface.

    Thank you

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Import Public Holidays for Business Hours

    Currently, there is only an option to manually add public holidays in the Business Hours settings. However, it would be better if we could import public holidays from a CSV or TXT file, or from a URL

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin & Core platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating