- or
No existing idea results
- ~ No ideas found ~
4744 results found
-
bulk
Please add option to bulk assign folders\site to devices, this is already on every other MDM it can be done easily via CSV on intune for example. We want the same option here in Atera, so if lets say I need to switch 300 devices to a more "aggressive" patch profile I dont need to manually assign them 1-by-1.
1 voteHi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
You can also follow this in our Public Roadmap.
Best regards,
The Atera Team
-
Copilot window obscures device function buttons
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.
2 votes -
Trouble Ticket Detail Templates
I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text, including headings, bullet points, hyperlinks, and styling (bold/italics)Optionally dynamic fields like [Customer Name], [Device], [Technician], etc., to auto-fill standard variables
User Experience:
When a template is selected, its content would populate the Description field automatically, which the technician can then tweak or expand upon.Markdown or basic WYSIWYG formatting should remain available.
Why This Matters:
Time-saving: No more copying and pasting from external documents or previous tickets.Consistency: Ensures all tickets follow the same structure, improving technician clarity and client-facing professionalism.
Training: Makes onboarding easier for new techs who can follow standardized ticket language and formatting.
Compliance and QA: Helpful for meeting internal documentation standards or industry compliance by enforcing specific data formats.
Example Templates:
Initial troubleshooting checklist
Onsite visit summary template
Firewall install/config notes
End-of-shift handoff summary
Service outage postmortem formatOptional Enhancement:
Allow default templates to be tied to specific ticket types or categories (e.g., selecting “Onsite Visit” from ticket type preloads the corresponding template).I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text,…15 votes -
Logical Stacking/Grouping of Patch Versions
Feature Request: Patch Management Improvements
1. Logical Stacking / Grouping of Patch Versions
Issue:
Patch Management currently displays multiple versions of the same patch as separate items, leading to:- A cluttered list
- Difficulty identifying the latest relevant version
- Confusing or inaccurate reporting
- Inefficient patch evaluation workflows
Requested Enhancement:
- Introduce logic to group or stack all versions of the same patch under a single collapsed entry.
- Display only the latest applicable version by default.
- Allow users to optionally expand to see historical versions if needed.
2. Ability to Hide or Filter Out Specific Patches
Issue:
Customers cannot hide outdated or irrelevant patch versions, resulting in:- Noise in the patch list
- False perception of devices being out of compliance
- Manual work to track what’s relevant
Requested Enhancement:
- Allow users to hide selected patches or categories of patches from visibility.
- Option to mark a device "up to date" regardless of deprecated patch entries.
3. Bulk Exclusion of Patches (Keyword-Based or Multi-Select)
Issue:
Excluding patches must be done one version at a time, which is extremely time-consuming—especially for vendors like Intel, Dell, or HP where dozens of minor revisions appear simultaneously.Requested Enhancement:
Provide multiple bulk-exclusion options:- Keyword-based exclusion (e.g., exclude all patches containing “Intel Extension”, “Dell Firmware”, etc.).
- Multi-select UI (checkboxes) to exclude many patches at once.
- Bulk actions (exclude, hide, group, etc.) for selected patches.
4. Improved Patch Display Customization
Issue:
Customers want more control over which patch categories or vendors appear, so only relevant updates surface.Requested Enhancement:
- Allow filtering or toggling by vendor, patch type, severity, or category.
- Offer a simplified “clean view” showing only meaningful, actionable patches.
5. Enhanced Reporting Accuracy
Issue:
Reporting is skewed by the presence of older patch versions being listed as "missing," even when newer superseding patches exist.Requested Enhancement:
- Update reporting logic to reflect supersedence and the latest required version.
- Ensure that hidden/excluded versions no longer impact compliance scores.
6. Roadmap Visibility for Patch Management Improvements
Issue:
Customer is in renewal evaluation and expressed frustration; they need clarity about whether patch usability improvements are planned.Requested Enhancement:
- Provide a public or semi-public roadmap note indicating upcoming Patch Management enhancements.
- Offer improved internal communication on how these FRs progress through Product review.
Feature Request: Patch Management Improvements
1. Logical Stacking / Grouping of Patch Versions
Issue:
Patch Management currently displays multiple versions of the same patch as separate items, leading to:- A cluttered list
- Difficulty identifying the latest relevant version
- Confusing or inaccurate reporting
- Inefficient patch evaluation workflows
Requested Enhancement:
- Introduce logic to group or stack all versions of the same patch under a single collapsed entry.
- Display only the latest applicable version by default.
- Allow users to optionally expand to see historical versions if needed.
2. Ability to Hide or Filter Out Specific Patches
Issue:
Customers cannot hide outdated or irrelevant…4 votes -
Make all custom fields available in scripts
Currently only agent custom fields are available to use in scripts. All custom field should be available (where sensible). For example, customer wide custom field containing data we want to access in a script.
4 votes -
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.”
2 votes -
Include active ticket time entries in contract remaining hours before ticket resolution
At present, contract remaining hours are only reduced once a ticket is marked as completed or resolved.
This creates a planning and capacity issue for us managing multiple open tickets for the same customer. Time may already be actively logged against several tickets that are still in Pending or In Progress status, but the contract balance continues to show those hours as still available until closure.
As a result, the remaining hours shown can be misleading for operational planning and resource allocation. In scenarios where several tickets are resolved at the same time, the contract can suddenly move into over-usage, despite the work having been carried out gradually over time.
Please allow contract remaining hours to reflect all logged time entries immediately, regardless of ticket status (Open, Pending, In Progress, or Resolved).
Alternatively, a separate field such as “committed / logged unbilled hours” or “projected remaining hours” would also help accurately forecast contract usage before ticket closure.
This would significantly improve workload planning, prevent accidental contract overruns, and provide a more accurate real-time view of customer support hours.
At present, contract remaining hours are only reduced once a ticket is marked as completed or resolved.
This creates a planning and capacity issue for us managing multiple open tickets for the same customer. Time may already be actively logged against several tickets that are still in Pending or In Progress status, but the contract balance continues to show those hours as still available until closure.
As a result, the remaining hours shown can be misleading for operational planning and resource allocation. In scenarios where several tickets are resolved at the same time, the contract can suddenly move into over-usage,…
1 vote -
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.
1 vote -
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…2 votes -
miradore
Miradore integration
2 votes -
Email notifications on Public notes when CCd
Currently no email notification is sent to a technician when they are mentioned in a Public note, this to me sounds like a simple request and is causing members of our team to miss ticket notes that they have been tagged in
1 vote -
Make the "Group" field on tickets visible on the Customer Portal
We would like the "Group" field on tickets to be visible on the Customer Portal view so our end users can see which team within our IT department is handling their ticket.
This helps because each team has their own set of SLAs and standards they follow, so it helps set better expectations and understanding with our end users when they have this information available to them.
1 vote -
Can only CC in contacts
Used to be able to add any email address to CC email field of ticket, then send email. Recently, perhaps since From field became selectable or more recent, can only add email address to CC email field that are contacts. Ticket may involve dealing with 3rd party service providers or the client's client, or B2B partners so should be able to add email addresses to ticket email CC field that are not contacts.
1 vote -
No longer able to assign any device to a ticket, can only assign contact linked devices
Used to be able to assign any device to a ticket, if device and ticket for the same client. Recently has been this contact linked devices change, since then the only devices that can be linked to a ticket are devices linked to the ticket contact. This makes no sense to be, as the ticket contact could change whilst the device, being the reason for the ticket, should not change. As in the case of a ticket being raised for a printer issue, or issue on a server, or a shared computer. The ticket device shouldn't change, the ticket device need not be linked to a user, and the user may even change during life of the ticket. No problem assigning multiple devices to a contact, that makes sense, even allow device to be assigned to multiple contacts, but ticket device assignment should be independent of the contact.
Used to be able to assign any device to a ticket, if device and ticket for the same client. Recently has been this contact linked devices change, since then the only devices that can be linked to a ticket are devices linked to the ticket contact. This makes no sense to be, as the ticket contact could change whilst the device, being the reason for the ticket, should not change. As in the case of a ticket being raised for a printer issue, or issue on a server, or a shared computer. The ticket device shouldn't change, the ticket device…
1 vote -
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.
1 vote -
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.
1 vote -
Successful/Unsuccessful profile execution in the device
Show whether the automation profile is successful or unsuccessful in the deivices activity log instead of a link to see the report.
1 vote -
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.
1 vote -
Need to be able to tie assets to a user
At this time we are using Atera for several things it was not initially designed for. We are using it as an asset management solution as well as the main development and design for what Atera is made for. We are able to add assets and assign them to a user however when we search the user nothing in your current set up lets us see all the assets we have associated to that user.
9 votesHi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
-
gili test
this is a test
2 votes
- Don't see your idea?