4821 results found

1. User Logout via User activity menu

   Please add the ability to logout a user from the "User Activity" menu on any device. This would be perfect for the cases where multiple users are logged into a machine, one may be in the "Disconnected" state and consuming a lot of RAM, this feature would allow us to logout those disconnected users without affecting the logged-in/active user(s).

   Thanks!

   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  ·  Devices  ·  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. Inactivate User based off of Entra ID Sync

   Atera's existing Entra ID integration is a one-way sync that creates new users and updates existing ones. On each run it imports users found in Entra ID and refreshes a set of profile fields (name, job title, phone, and mobile) on records it matches by email address.

   However, it does not sync a user's account status, and it has no deprovisioning step. A user who is disabled or removed from Entra ID the sync leaves their Atera record in place and active. This obviously causes a data consistency issue as users are now showing active in Atera that have been long gone.

   Atera should have a setting that will automatically deactivate an Atera user when they are disabled or removed in Entra ID.

   Atera's existing Entra ID integration is a one-way sync that creates new users and updates existing ones. On each run it imports users found in Entra ID and refreshes a set of profile fields (name, job title, phone, and mobile) on records it matches by email address.

   However, it does not sync a user's account status, and it has no deprovisioning step. A user who is disabled or removed from Entra ID the sync leaves their Atera record in place and active. This obviously causes a data consistency issue as users are now showing active in Atera that have been… 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  ·  Customers  ·  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

3. Allow scheduling of child tickets

   When creating a child ticket allow it to be scheduled, aids in project management and disable/enable scenarios for sharing, access or user leave.

   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  ·  Tickets  ·  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

4. Search devices from app instead of customers

   While I have my computers grouped by customer I would like the option to search for a device directly rather than having to click into the customer and then into devices.

   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  ·  Mobile App  ·  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. Cancel Ticket Creation Confirmation

   When creating new tickets the cancel button is located directly next to the create button. This cancel button doesn't require any confirmation, and immediately cancels and deletes any information entered into the ticket. With a sensitive mouse it is too easy to click the cancel button by mistake forcing the ticket creation process to restart.

   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  ·  User Interface  ·  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. Resize comment box

   Ability to resize the comment box, not just full screen

   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  ·  Tickets  ·  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

7. Linklist last visits computers, etc., in the left-hand menu

   It would be very helpful to have a list of links to recently visited customers, computers, etc., in the left-hand menu bar. Otherwise, you end up clicking yourself to death. That should be easy to do.

   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  ·  User Interface  ·  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. Allow ticket properties to be made visible based on the ticket Technician Group

   Atera currently displays certain custom fileds based on the ticket form that's selected.

   This requires us to create Tickets Forms e.g. Workforce tickets that aren't user facing so that we can see the corrosponding fields inside a ticket (See attached screenshots)

   Because we have to use a form for displaying these fields, a non user facing form is displayed in our user ticket form which isn't ideal.

   We use technician groups to act as different queues for different types of tickets e.g. Workforce tickets. Can we make certain custom fields visible based on the Technician Group rather than having to select a from that contains the field?

   Atera currently displays certain custom fileds based on the ticket form that's selected.

   This requires us to create Tickets Forms e.g. Workforce tickets that aren't user facing so that we can see the corrosponding fields inside a ticket (See attached screenshots)

   Because we have to use a form for displaying these fields, a non user facing form is displayed in our user ticket form which isn't ideal.

   We use technician groups to act as different queues for different types of tickets e.g. Workforce tickets. Can we make certain custom fields visible based on the Technician Group rather than having to… 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  ·  Tickets  ·  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. Feature Request: Repeating Alerts for Critical Devices and Scripts

   Hi Atera Team,

   I'd like to request the ability to configure repeating alerts for designated critical devices and scripts.

   Current Problem

   Currently, Atera sends a single notification when a device or script enters a failed state.

   In many environments, that single email can easily get lost among other monitoring alerts or simply among the hundreds of other emails people receive throughout the day. As a result, the customer may never see the notification until much later, allowing a critical issue to go unresolved for hours or even days.

   Proposed Feature

   Allow any supported object to be marked for repeating notifications.

   This could apply to:

   PCs
   Servers
   Generic Devices
   Scripts

   For example:

   Repeat alert every: 15 minutes, 30 minutes, 1 hour, 2 hours, etc.

   The repeat notifications would continue until the device or script returns to a healthy state.

   Suggested Implementation

   Atera already allows us to choose which notifications we receive, such as Critical and Resolved alerts.

   It seems like the most natural place for this feature would be in that same notification configuration area. For example, a simple option such as:

   ☐ Repeat this alert every: ___ minutes until resolved

   This would fit naturally into the existing alert configuration without changing the current workflow for users who don't need the feature.

   Example

   I monitor customer camera systems.

   Some alerts are informational, but others are extremely important.

   Examples include:

   Camera Server offline
   RAID array failure detected by a custom script
   Core network equipment offline

   If the original email is overlooked or buried in the customer's inbox, the customer could unknowingly operate for hours or even days with a critical failure. Repeating notifications at a configurable interval would greatly increase the likelihood that the issue is noticed and addressed promptly.

   Expected Behavior
   A critical device or script enters a failed state.
   Atera immediately sends the initial notification.
   If the device or script remains in the failed state, Atera sends another notification at the configured interval.
   This continues until the issue is resolved.
   Once the device or script returns to a healthy state, Atera sends the normal recovery notification and stops the repeating alerts.
   Benefits
   Prevents critical alerts from being forgotten or overlooked.
   Helps ensure outages are resolved more quickly.
   Gives customers confidence that important failures won't disappear into their inbox.
   Allows repeating notifications to be enabled only for the devices and scripts that truly require them, preventing unnecessary email traffic.
   Gives customers flexibility to decide which devices and scripts warrant persistent notifications and which only need a single alert.

   This feature would work especially well alongside an "Only Alert if Offline for X Minutes" request that I also made here. Less important or unstable devices could wait before generating an alert, while truly critical devices and scripts could continue reminding users until the issue has been resolved.

   Thank you for considering this request. I believe this would significantly improve Atera's monitoring capabilities for businesses that rely on timely notification of critical infrastructure failures.

   Hi Atera Team,

   I'd like to request the ability to configure repeating alerts for designated critical devices and scripts.

   Current Problem

   Currently, Atera sends a single notification when a device or script enters a failed state.

   In many environments, that single email can easily get lost among other monitoring alerts or simply among the hundreds of other emails people receive throughout the day. As a result, the customer may never see the notification until much later, allowing a critical issue to go unresolved for hours or even days.

   Proposed Feature

   Allow any supported object to be marked for repeating notifications.

   … 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  ·  Alerts  ·  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. Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)

    Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)

    Hi Atera Team,

    I'd like to request a feature that would significantly improve monitoring for environments with devices that experience brief or intermittent connectivity issues.

    Use Case :

    Many of my customers have surveillance systems that consist of:

    A Camera Server (Windows PC)
    Multiple Generic Devices representing IP cameras on the customer's network

    Some cameras may briefly disconnect dozens or even hundreds of times per day due to aging network cabling, camera hardware issues, or temporary network instability.

    Current Problem :

    Atera generates an alert every time one of these devices goes offline.

    This results in:

    Hundreds of unnecessary email alerts each day to me and my customers
    Alert fatigue
    Important alerts (such as the Camera Server going offline or a RAID failure) getting buried in the noise

    Proposed Feature Request:

    Add a configurable option for any monitored device (PCs and Generic Devices or Scripts because I have a script that detects when my USB attached Raid Arrays go off which is where all camera footage is stored honestly this is absolutely the most important alert they get if that is offline they are no longer recording):

    Only alert if device has been offline for X minutes

    Example configuration:

    Camera Server , Raid Array
    Alert immediately (0 minutes , Default Setting for Atera)

    Generic Devices
    Alert only if offline for 30 minutes or whatever we set it at.

    If the device reconnects before the configured delay expires, no alert should be generated.

    Why This Matters:

    For many of my customers, this isn't just a convenience.

    They are required by state regulations to document camera outages that exceed 30 minutes. If a camera remains offline longer than that threshold, they must complete and submit an outage report to the regulating agency.

    Because of this requirement, simply disabling alerts on problematic cameras is not an option. We still need notifications but only when the outage becomes significant. (like over 30 mins exactly in my case)

    Expected Behavior for this feature :

    • Device goes offline.
    • Atera starts an offline timer. (which I set that timer period)
    • If the device comes back online before the configured threshold, no alert is sent.
    • If the device remains offline longer than the configured threshold, send the normal offline alert.
    • Once the device recovers, send the normal recovery notification.

    Benefits

    This feature would provide several advantages:

    • Significantly reduce alert fatigue for MSPs and customers.
    • Ensure important alerts aren't buried beneath hundreds of transient device notifications.
    • Help our organizations remain compliant with regulations that require reporting prolonged outages.
    • Reduce unnecessary email volume, which could lower the number of outbound notifications Atera has to generate and process. At scale, that could reduce load on your notification infrastructure while also improving the customer experience.

    This would dramatically improve the signal-to-noise ratio of monitoring without changing existing alert behavior for customers who don't enable the feature.

    Thank you for considering this request. I believe this would be valuable for surveillance deployments, IoT environments, and any customer who monitors devices that may experience brief connectivity interruptions while still requiring reliable alerting for prolonged outages.

    Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)

    Hi Atera Team,

    I'd like to request a feature that would significantly improve monitoring for environments with devices that experience brief or intermittent connectivity issues.

    Use Case :

    Many of my customers have surveillance systems that consist of:

    A Camera Server (Windows PC)
    Multiple Generic Devices representing IP cameras on the customer's network

    Some cameras may briefly disconnect dozens or even hundreds of times per day due to aging network cabling, camera hardware issues, or temporary network instability.

    Current Problem :

    Atera generates an alert every time one… 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  ·  Alerts  ·  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

11. Knowledge Base

    When first opening the knowledge base, the search window appears at the top, which suddenly jumps down once the "Popular Articles" section gets filled out, this means that I end up clicking on some article as that has jumped in where the search window was. Don't move the search box, have it STATIC at the top. It is very annoying.

    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  ·  User Interface  ·  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. It would be great to be able to assign multiple devices a particular software or other automation by agent, not folder or site.

    It would be great to be able to assign multiple devices a particular software or other automation by agent, not folder or site. Or, be able to assign multiple folders per device. Even better, would be able to assign by user from EntraID.

    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  ·  IT Automation and Patch Management  ·  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. 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.

    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

14. Ticket Times

    If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful

    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  ·  Tickets  ·  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

15. ticket time

    If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful

    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  ·  Tickets  ·  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. eset for germany
    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  ·  3rd Party Integrations  ·  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. Feature Request: Allow running / re-running ticket playbooks on existing tickets.

    Feature Request: Allow running / re-running ticket playbooks on existing tickets (or in a ‘simulation’ mode) so we can iterate and debug complex automations faster without generating new test emails/tickets each time.”

    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  ·  AI Copilot  ·  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. [API] SearchOption

    When searching contacts by phone number through the API, the searchOptions.phone filter only matches the Phone field of a contact. It does not match MobilePhone, even though both fields are part of the same
    contact record and both are valid phone numbers for that contact.

    Use case

    We are building an automation that needs to identify the calling end-user from their phone number and resolve them to an Atera contact in order to retrieve their tickets,
    post comments on their behalf, etc. In real customer data, the mobile number is stored in MobilePhone for the majority of contacts (landline goes to Phone when present). With the current behavior, those
    contacts cannot be found via the API search and we have to fall back to listing all contacts and filtering client-side, which is slow and does not scale.

    Steps to reproduce

    1. Create or pick a contact whose MobilePhone = 600101010 and whose Phone is empty (or different).
    2. Call: GET /api/v3/contacts?searchOptions.phone=600101010
    3. Expected: the contact is returned.
    4. Actual: empty result. The same call works only if you put the number in Phone.

    We have tried number variants (600101010, 34600101010, +34600101010) and combinations of EnableContactsSearch/EnablePartialSearch flags — none of them make the search look at MobilePhone.

    Suggested fix

    searchOptions.phone should match against Phone and MobilePhone (logical OR), the same way the in-app contact search does. Alternatively, expose searchOptions.mobilePhone as a separate filter so callers can
    choose.

    Current workaround

    We list contacts page by page and filter client-side on Phone || MobilePhone. This means N requests per identification and we hit rate limits on tenants with many contacts.

    Environment

    • Atera REST API v3 (https://app.atera.com/api/v3)
    • Tested 2026-04-16

    Thanks!

    When searching contacts by phone number through the API, the searchOptions.phone filter only matches the Phone field of a contact. It does not match MobilePhone, even though both fields are part of the same
    contact record and both are valid phone numbers for that contact.

    Use case

    We are building an automation that needs to identify the calling end-user from their phone number and resolve them to an Atera contact in order to retrieve their tickets,
    post comments on their behalf, etc. In real customer data, the mobile number is stored in MobilePhone for the majority of contacts (landline goes… 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  ·  Other  ·  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. Patch management

    To be able to schedule Patch management tasks, this would be useful for Mac devices that require Upgrade patches to be run via Patch management instead of IT Automation profiles.

    This workaround is useful for Mac devices that are offline, in order to help automate pushing Upgrade patches

    86 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

    7 comments  ·  IT Automation and Patch Management  ·  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. Software Bundle Deployment Very Slow

    Software Deployment is incredibly slow, and lacks any meaningful feedback during and after the process completes. No matter how many softwares are included in the list, it seems to take nearly an hour to deploy. Meanwhile, when we use a script to deploy a series of Ninite packages, they are done in 20 minutes...

    At this point we only install two things from our default software bundle, and it STILL TAKES FOREVER. We don't even know when it really finishes without pulling event logs.

    The whole point behind automation is to do it faster than a person... right now the slowest person on our team can get it done in 15 minutes. We expect this to take less than 10 and as much as 15 if we are also installing something big like Microsoft Office.

    Software Deployment is incredibly slow, and lacks any meaningful feedback during and after the process completes. No matter how many softwares are included in the list, it seems to take nearly an hour to deploy. Meanwhile, when we use a script to deploy a series of Ninite packages, they are done in 20 minutes...

    At this point we only install two things from our default software bundle, and it STILL TAKES FOREVER. We don't even know when it really finishes without pulling event logs.

    The whole point behind automation is to do it faster than a person... right now the… 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  ·  IT Automation and Patch Management  ·  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