4795 results found

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

   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

2. support proxmox host

   a modifyed client that supports proxmox host, with all the standard proxmox services

   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  ·  Devices  ·  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. 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.

   … 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

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

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

5. newest

   the ticket order newest to oldest i dont like at all

   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

6. Veeam 365 Backup including Public Folders

   Veeam 365 Backup includes Public Folders, cannot find anyone else offering this.

   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

7. Need the funtion to add calendarentries for team members

   Until recently, it was possible, to create calendar-entries for tickets in calendars of team members. Since a few weeks, this is not possible anymore.
   This was a key feature for us, when managing tickets. We urgently need this function back. A team calendar is not a solution, as we dedicate the ticket to a person.

   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

8. Ticket body - not wrapping text properly words cut off

   Finding clients that type a longer ticket description the ticket body is not wrapping and several words on the right are cut off.

   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. US pacific time zone support.

   There always seems to be a day delay in regards to ticket responses. I think ticket would be resolved twice as fast if there were a dialog closer to real time.

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

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

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

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

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

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

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

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

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

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

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

20. Dynamic field mapping for Cloud Actions via Custom Fields

    Summary
    Cloud Actions should be able to pull values for API calls dynamically from user-defined Custom Fields, instead of only supporting static input or full list retrieval. This would enable targeted update/write operations against the Atera API (and external APIs) without having to manually identify the relevant record.
    Current behavior
    When I set up a Cloud Action against the Atera API (e.g. "Update Customer"), I can essentially only retrieve all entries via the API. There is no way to dynamically bind a call's parameter to a specific record or an existing Custom Field. As a result, targeted updates are cumbersome or not possible at all.
    Desired behavior
    When creating a Cloud Action, I want to define per API parameter where the value comes from - in particular, from a user-created Custom Field. Example:

    Cloud Action: "Update Customer" (Atera API)
    Parameter CustomerID → Source: Custom Field customerid
    The action reads the value from the field, matches the corresponding entry, and performs the update specifically for that record.

    Specifically, this would require:

    Selecting the value source per parameter (static value, variable, Custom Field).
    Mapping Custom Fields to API parameters directly in the action editor.
    Validating/matching the entry before the write operation, so the correct object gets updated.

    Use case / benefit
    This would make it possible to build real automated update workflows (maintaining customer data, keeping fields in sync, reconciling external systems) instead of only reading and "dumping everything." For MSP scenarios with individual Custom Fields, this is a significant improvement in efficiency and data quality.

    Summary
    Cloud Actions should be able to pull values for API calls dynamically from user-defined Custom Fields, instead of only supporting static input or full list retrieval. This would enable targeted update/write operations against the Atera API (and external APIs) without having to manually identify the relevant record.
    Current behavior
    When I set up a Cloud Action against the Atera API (e.g. "Update Customer"), I can essentially only retrieve all entries via the API. There is no way to dynamically bind a call's parameter to a specific record or an existing Custom Field. As a result, targeted updates are cumbersome… 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  ·  IT Autopilot  ·  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