Skip to content

Ideas and Feedback

Ideas and Feedback

Categories

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

4798 results found

  1. Introduce a technician-side To-Do List feature, to manage multi-activity tickets without exposing them as separate tickets in the Service Desk/customer portal

    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)
  2. When a user opens a ticket from the user portal with a dedicated Onboarding/Offboarding form, only one ticket is created. Internally, child subtickets are created for each activity (Atera lacks a To Do list). The customer side will see many open tickets and won't know which is the parent ticket and which are the child tickets.

    Consider:
    * View Parent-Child relationship in the service desk
    * Ability to filter only the parent ticket
    * Create a To Do List on the technical side to manage tickets with multiple activities that are not visible to the Service Desk

    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)
  3. We use one automation rule to create Child tickets (subtasks) when a parent ticket is created from another department ( example Onboarding/offboarding), and a second rule to assign a technician to each Child ticket.
    The second rule never triggers, because Atera does not allow an action performed by one automation rule (creating a Child ticket) to act as a trigger for another rule. As a result, Child tickets are always empty and created without a technician assigned, requiring manual assignment every time.
    Please consider:
    * Allowing automation rules to trigger other automation rules, or
    * Allowing technician or other fields…

    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)
  4. I would like to know in a percentage how many of my issues are fixed on a 1st time basis.

    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)
  5. After a user leaves, I don't want to still see them in the site lists. Need a way to manage that or the site lists will get bloated with termed employees.

    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)
  6. Hi Atera Team,

    Following up on our recent chat with Constantin (Aug 27), we'd like to formally submit two feature requests, as we understand these aren't currently supported but would significantly improve our workflow.

    1. Automatic Reply Sender Address per Technician Group

    We have multiple Support Addresses set up (e.g., knowledge@inc.com for our Knowledge Team, support@.global for Helpdesk Support), each tied to its own Ticket Automation Rule and Email Template.

    Currently, when a ticket is generated via a specific address (e.g., knowledge@inc.com), the automatic reply is still sent from the default outgoing address (support@.global), regardless of which…

    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. we would like to see an Atera agent for Chromebooks, it would be very beneficial.

    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  ·  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)
  8. Please add a device availability status field to the Software Inventory report.

    The report should include an additional column showing whether each computer is currently:

    Online
    Offline

    The status should also be included when exporting or scheduling the report in Excel, CSV, or PDF format.

    This would make it possible to distinguish software inventory data received from currently connected computers from cached inventory data belonging to offline computers.

    It would also be useful to add the following fields:

    Last Seen
    Availability Monitoring Enabled/Disabled
    Folder
    Device Type

    Please make these fields available both in the built-in Software Inventory report and in…

    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)
  9. Currently, reboot schedules can only be configured in 30-minute increments. Please allow administrators to manually specify an exact reboot time (e.g., 10:15 PM, 11:05 PM, etc.). This would provide greater flexibility for maintenance windows, patching schedules, and minimizing user impact.

    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)
  10. Time and time again we realized that we cannot automate certain Atera features via API from our agents (AI agents..). I think the time has come that companies need to provide a feature-complete API and not put things behind their UI or their own agents so that we buy their extended packages.

    A feature incomplete API is a bug, not a missing feature..

    Here some examples we cannot do via API that are possible via UI:

    • Run a script or command on an agent
    • Assign or remove an automation profile
    • List, assign or change a threshold profile
    • See which automation,…
    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)
  11. Currently, Atera only triggers the passkey creation prompt once during setup. If a technician registers a hardware-bound passkey (e.g., local Windows Hello / TPM module), it is impossible to register a second device (like a secondary workstation or laptop) without completely resetting 2FA for the account. Resetting 2FA invalidates all previously configured credentials, making it impossible to use multiple hardware-bound keys simultaneously.

    Technicians are currently forced to use cloud-synced passkey managers (like Chrome or iCloud Keychain), which is not compliant with many enterprise security environments that strictly mandate hardware-bound TPM credentials or physical FIDO2 tokens.

    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  ·  Security  ·  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. The ability to force the logout of a user session & lock user accounts from the Atera portal. I am currently doing this with scripts however, unless the user is currently signed in, it can be difficult for the scripts to identify the owner's account 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  ·  Security  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Subject: Feature Request – Access Roles should hide menu items/widgets based on permissions

    When I disable a permission (e.g., Patch-Management → "View and install patches directly on devices") for an Access Role, the Patch-Management menu item still appears in the left sidebar for that user, even though they have no access to it.

    Request:

    The left navigation menu should dynamically show/hide items based on the permissions granted to the user's Access Role. If no permissions are enabled for a module, the menu item should be hidden entirely — not shown as an inaccessible/disabled entry.
    This would allow admins to create…

    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. There's no API to push scripts to the IT Automation and Patch Management dashboard. Having that will simplify script management and deployment.

    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)
  15. Add an option to display an interactive Windows Toast notification on the end-user device when a script or automation profile is being executed.

    We’d like to have a simple tick box/checkbox that can be enabled when deploying a script or automation profile, allowing Atera to display a Windows Toast notification to the user on the affected device.

    Suggested functionality

    When enabled, the user would see a Windows notification such as:

    IT Helpdesk (or Atera) Automation in Progress
    An automated task is currently running on your device.

    Progress: 65%
    █████████████░░░░░░

    Current task: Installing Windows Updates

    The notification could dynamically update as…

    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)
  16. We’d like Atera to support entering time using decimal hours rather than requiring users to enter hours, minutes, and seconds in the HH:MM:SS format.

    For example:

    0.25 = 15 minutes
    0.50 = 30 minutes
    0.75 = 45 minutes
    1.00 = 1 hour
    1.50 = 1 hour 30 minutes
    1.75 = 1 hour 45 minutes
    Why this would be useful

    Decimal time entry would make logging time much faster, easier, and less error-prone, particularly when entering a large number of time entries.

    Currently, having to enter something like 01:45:35 is cumbersome when the actual requirement is simply to record approximately 1.75…

    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

    0 comments  ·  PSA Tools  ·  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. I'd like to be able to export our ticket automation rules into a csv or similar file. This would help with designing automations and with training new technicians that will also be developing automation rules.

    4 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)
  18. In the ticket automation should be able to send an auto reply if the ticket arrives out of hours, this way we can direct them appropriately.

    Therefore we need a way to trigger the ticket depending on the time of day it arrives.

    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)
  19. Atera supports multiple customers. That's why we use it.

    Different subscriptions are applied to different customers. But some subscriptions are applied to multiple customers.

    Whoever uses Atera gets a bill, and with some digging, can find the breakdown of the monthly cost of each subscription... but we bill customers based on their part of the subscription. The bill we get only shows a total cost. I can see X total seats in use, but not X seats for customer A, Y seats for customer B, Z seats for customer C, etc.

    It would be extremely helpful--necessary, actually--to see a per-customer…

    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)
  20. Copilot Developer feedback list: 1) Give the AI secure, read‑only access to ticket‑linked mailboxes, 2) Add URL sandbox/reputation checks for every link in a message, 3) Expose more endpoint automations so fewer answers fall back to “manual,” 4) Reduce tool‑call overhead so technicians get direct actions, not workflows, 5) Improve accuracy/coverage so the assistant is useful >90% of the time, 6) Make limitations explicit in‑product so techs don’t waste time discovering them.

    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  ·  IT Autopilot  ·  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 239 240
  • Don't see your idea?