Skip to content

Ideas and Feedback

Ideas and Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

4703 results found

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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We've been trying to find a way to implement automated tickets follow-ups (using "activity status" and "hours since status changed") but can't seem to get it to work. Has anyone been able to make it happen? Currently, there is no trigger for Activity Status just Status. We cannot mark the ticket as Pending everytime to trigger this automation. Defeats the purpose of an automation it will have be done manually. I found a reddit article replied by Atera (3 years ago) and still no change. https://www.reddit.com/r/atera/comments/zevva9/can_ticket_automation_do_followups_and_close_if/

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Would be very handy to have an option to exclude customers from Technicians rather than have to manage "specific" customers they can access. The larger an Atera instance grows, the more difficult and annoying it is to manage specific exclusions from the list for every group.

    Having an option such as "Exclude these customers" from the technician access would be a much quicker and easier option rather than "specific customers" where you have to add every customer and then remove those that users shouldn't access.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Device metrics

    Currently, RAM and CPU usage are displayed as a single graph. A separate display would be very helpful. Network usage could also be shown as a graph, as well as a drive overview. Displaying these as tiles would be a worthwhile addition.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Hi,

    We make heavy use of the Atera API and overall it’s solid. Device inventory, patching data, alerts etc are all there and work well. It’s one of the reasons we’ve built around Atera rather than trying to work around it.

    One thing we keep hitting though is the lack of installed software inventory via the API.

    In the UI, Atera clearly has visibility of what software is installed on each device, but via the API we can’t get that same data. We can pull hardware details and patching info, but not the actual list of installed applications.

    That’s a…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. First, I want to say that we genuinely love the Atera platform. It’s central to how we operate, and we actively want to deepen our commitment to it. The automation, visibility, and overall direction of the product are excellent, which is why this issue stood out so starkly for us.

    We recently experienced a serious operational incident caused by the current behaviour of the Remote Access settings UI.

    What happened
    We manage thousands of devices across many customers, often onboarding environments where previous MSP tools or customer-managed tools (for example, ScreenConnect) are already present on endpoints. In our environment, Splashtop…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Hi everyone — we’d love feedback on the new Tickets page UI (the redesigned, configurable table).

    What’s new (vs old Tickets page):

    • Detailed vs Compact view (Compact = more rows per screen)
    • Show/hide columns
    • Reorder columns
    • Sorting + saved views
    • New columns: Approval status, Created date, Last action date, Parent/Child tickets

    What we need from you:
    - Reply with anything you’ve noticed, but if you can, use this quick format:
    1) Your setup
    - Detailed or Compact?
    - High-volume queue or occasional triage?

    2) What works
    - What’s better than the old page?
    - Missing columns?
    - Too many clicks?…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. In the profile, when we check “Run profile on recently installed agents”, the execution does not happen immediately, it takes too long and often forces us to either trigger the profile manually right away or run the scripts individually. Why does this feature not work properly? It is completely opaque and that is not acceptable. Make sure that when we request execution for a recently installed agent, the profile runs immediately once the agent is detected and installed.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Agent  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. We request two specific additions to the API to improve ticket management and documentation:

    Ticket Endpoint: Add a LastInternalComment field (similar to the existing LastEndUserComment).

    Comments Endpoint: In GET /api/v3/tickets/{ticketId}/comments, include the boolean status IsSolution for each comment object.

    Context & Why this is useful:

    LastInternalComment: We need to quickly see the status of a ticket based on the last technician note, not just the user's reply. Currently, we have to download all comments to find the last internal update.

    IsSolution: When syncing tickets to a knowledge base or sending final reports to customers, we need to programmatically identify which…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. On a device page, the AI Copilot windows obscures the Connect, Manage, Copilot, and Create ticket buttons along the top. Similar issue on the Ticket page, etc.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  User Interface  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add signature options to mobile apps for technicians. Currently it doesn’t pull them through from profile so responses done on mobile app don’t include a signature

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Mobile App  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. I would like to request an enhancement that allows the assigned report name, such as the customer name or a unique report identifier, to be clearly displayed. I have created several reports, some of which are sent to customers and others to myself, for example status updates or internal reports. At the moment, the report name is not visible in the email preview, the email content, or within the report itself.

    Adding this information would greatly improve clarity and usability, especially for users who manage multiple reports in parallel. This enhancement would reduce confusion, minimize manual verification efforts, and help…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reports  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. In the mobile app there's no ability to sort. For example, you can't sort tickets newest to oldest or vice versa.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Mobile App  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. An option to integrate with email providers i.e. Microsoft via API calls rather than forwards.

    This would allow emails/tickets to be pulled in fast, secure and minimises the amount of issues that can arise from email forwards and can help prevent ETP systems from double scanning emails that have already been checked (reducing hops and preventing further delivery issues)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. We need the ability to assign patch policies to different devices GLOBALLY not just per customer/folder.

    Example: You have 2 Windows Patch Policies

    Workstations: Update within a week and push all available updates
    Servers: Update within 2 weeks and push available patches

    This allows you to keep critical infrastructure patching separate from the rest of the fleet and have it assigned automatically as the agents get deployed.

    Datto has this functionality - Atera needs it

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. We would like the ability to turn off ticket tabs - we don't find them useful as they are presently.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. When creating new ticket forms and selecting a dropdown with dependencies, there is only one child layer option. It would simplify our setup if we could include multiple child levels. I have attached an example of the current option and the desired option.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 235 236
  • Don't see your idea?