5031 results found
-
Documentation Management
Are you struggling to keep track of your customers info (i.e., files, addresses, passwords)? Interested in a documentation management integration?
1,249 votes -
"For X Days" Alert Threshold Option
Allow the option to set a period of time to NOT send alerts. For example, "If device has out-of-date patches for more than 3 days, Alert".
This is an option for hardware thresholds (CPU temp above 60C for 15 minutes). Our reports throw a lot of red flags for items that are scheduled daily or every 3 days. I want the reports/alerts to trigger if there has been a persistent issue, not if there happens to be an issue at the time of reporting.
2 votes -
Calendar (Calendly) Scheduler
The service allows customers to easily schedule appointments with our technicians for either an in-person visit or remote repair. Similar to Calendly.com, customers can choose from the available free times in our technician's calendar to set up a convenient appointment. Once the customer selects a time, both parties will receive a calendar invite to confirm the appointment. This process ensures a smooth and efficient scheduling experience for our customers.
8 votes -
Network documentation and diagrams section
It would be very useful to have a section where you can generate and save network diagrams, SIR plans, network security configuration etc...
Perhaps providing documentation templates or a way for users to share document samples and templates.85 votes -
Passwords
Notes under passwords needs to be expandable. Most account have addition information and PIN's etc.
Example belowAcc#
PIN#
Serial #
Product key#
Main contact#3 votes -
Patch schedule calendars integration to be able to exclude dates from patching.
Patch schedule calendar integration to be able to exclude dates from patching. Some companies have blackout dates where no changes are allowed. Also be nice to see the actual schedule of patching in a calendar form.
4 votes -
Ticket Automation Rules - "ticket created" email - stop email loops
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email"…
4 votes -
Need a device filter for assigned threshold profiles
Need a device filter added for assigned threshold profiles. We need to easily filter devices to see which may not have a threshold profile assigned at all. Or that do not have the correct threshold profiles assigned. And then be able to add them via a multi check box.
3 votes -
Custom Assets View
Custom Assets
Should be able re-organize which fields shows in the dashboard, instead of the default Name, Type, Folder and Contact.
Also an option for the date field to have an alert. For example if you are tracking support services renewals for the customer, it should alert you when renewal is within 30 days.
15 votes -
show device count on customers
The customers table should show how many devices each customer has, and optionally how many are online. Bulk onboarding agents is more painful than it needs to be without this.
3 votes -
Create ticket trigger under ticket automation rules for patching
Trigger for generating a new ticket if patches are applied manually through devices tab by a technician. Seeing as this is a manual action by a technician and not done through automatic patch management it would warrant a ticket being generated for a specific agent/contact with a relevant time entry.
4 votes -
Customizable Availability Monitoring
The ability to get an alert if a device is offline for so long, like say an hour, instead of getting an alert for a device going offline, when it is only restarting or something similar
2 votes -
knowledge base Report
Create an option to pull reports on knowledge base as to who viewed and how much times the articles was viewed
5 votes -
New internal note alert
Alert by email the technician that a new internal note is added to his ticket.
23 votes -
Author of Knowledge Base Articles
It would be good to know the author/source of a Knowlege Base article. We have several contributors and it would be good to know the source to check validity, follow up with them for clarification, reward those that are frequent/prolific contributors of KB articles. We can already see the creation date. It should be fairly easy to add a field for Author/Creator of KBs.
1 vote -
manage Microsoft 365 users directly from Atera
It would be great to be able to manage Microsoft 365 users directly from Atera. Doing things like Password Resets, Create new users, Adjust / Add licenses, Email forwarding etc, instead of having to login to each customers Admin portal everytime. This can become extremely time consuming.
6 votes -
Better structure to the KB
It would be nice if we could build a deeper KB tree. Currently it can only be two layers deep.
L1: Category
L2: Section
It would be nice if we could go at least 1 layer deeper and have subsections.9 votes -
When assigning agents to tickets, show logged in user in dropdown.
The dropdown when assigning an agent to a ticket should show the current user, as only this way we know which device has the problem (as users don't always work at the same PC)
1 vote -
Dateien an Ticket hinzufügen
It would be convenient if files could be attached to a ticket.
A current workaround is to create an internal note and then attach the file, but then it becomes necessary to search for the file in the ticket history whenever the ticket becomes longer.1 vote -
ticket activity messages
I think it would be very useful that ticket's history section reflects which Rules has been applied (appearing on history as the rule's title), and not just the action. This would work as a kind of "debug", helping us to confirm which rules are really applied on each scenario and accelerating/helping a lot our learning curve.
1 vote
- Don't see your idea?