- or
No existing idea results
- ~ No ideas found ~
4702 results found
-
Auto install default remote with Agent
Maybe this is a bug, but I notice on the Android Mobile app (using a fully updated Google Pixel 6a) if you have not run the remote connection from a PC initially, the option to Connect on mobile is greyed out. After connecting at least once to trigger the install it works on mobile as expected.
Maybe this is how it is supposed to be, but it would be nice if the default remote got installed fully when the agent does. Often times when out remote and installing new agents, it is nice to quickly verify full connectivity from mobile before leaving site without having to check from a desktop/laptop first. Perhaps there is a script that will automatically do this (we use Splashtop RMM as our default)
Maybe this is a bug, but I notice on the Android Mobile app (using a fully updated Google Pixel 6a) if you have not run the remote connection from a PC initially, the option to Connect on mobile is greyed out. After connecting at least once to trigger the install it works on mobile as expected.
Maybe this is how it is supposed to be, but it would be nice if the default remote got installed fully when the agent does. Often times when out remote and installing new agents, it is nice to quickly verify full connectivity from mobile…
5 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 -
Technician Role permissions
Roles within Admin need to have the ability to have more control of what features each group has.
Under RMM, the "Edit Device" feature is too strict. We want to be able to allow certain technicians to edit device names but not be able to delete them.Setting that can be turned off so that no technicians have the ability to delete anything.
13 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 -
Mobile needs a Dashboard page
Please include a dashboard tab in the mobile app. I have no way to monitor everything from a tablet on my desk. I would like to be able to see everything and not choose ALerts or Tickets. TY!
6 votes -
Free Account User for Admin Purposes
I gather it won’t happen everywhere but certainly happens at our end (and most companies I work with); but we employ an accounts lady who handles all purchase ledger invoicing (buying a pen, paying for the supply of gas or electricity but also for Office365 or AWS) which is mostly done via our business partners portals.
So basically one (free of charge) account should be made available per company that strictly covers administrative duties limited to Atera subscriptions and licensing, add and remove agents’ licences, edit payment details such as credit card details, invoices, etc.33 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 -
link to a ticket on mobile opens the app rather than web page
When you receive an email and it contains a link to a ticket, tapping the link should check if the app is installed and if it is, open it to display the ticket.
14 votes -
Alerts for new ticket and ticket replies
You know how alerts will play a sound when it happens? That would be great if you could make tickets do the same thing. If someone creates a ticket I would like to be able to turn on a sound notification just like the alert sound settings. I already get ticket notifications on my phone so I do not feel like this is would be hard to integrate into the web dashboard.
1 vote -
Agent chat
Please make an option to disable and enable automatic ticket creation the Agent chat that create ticket after two minutes of conversation.
Please, We want to chat with the user and leave the user create the ticket or the IT to create the ticket manually.
We need this option to interact with the user with no limit, please make this happened.
1 vote -
misfunction on Action "Send email to Technician"
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any way, but the email of AssignedTechnician in order to execute the action correctly.
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any…
1 vote -
i18n on mail Templates vs Rules
The current implementation on Email Templates vs rules makes it difficult to manage a multilanguage scenario. For N templates representing the same notification in different languages, it's needed to generate 1 rule for each language in order to respond the Requester in an appropiate way on their language. In our case, with an international sctructure of different departments abroad, it's implying an enormous collection of rules than, in essence doing exactly the same thing but in different languages.
I think would be very useful to develop i18n characteristic on email templates vs rules, as explained:
- 1:N relationship on "1 template target topic" : "N language implementations".
- Related views grouped by "Target topics".
- If so, just 1 rule will be needed to manage multilanguage scope about an specific trigger. I mean, when I create rule, Atera will implicitly manage "reaction to" multilanguage scenario, always based on the language of Requester on their profile. An example: For an specific Rule "X", when Atera notifies to the Requester (or Technician), it will evaluate the language on his profile, and will make use of templates for this language.
The current implementation on Email Templates vs rules makes it difficult to manage a multilanguage scenario. For N templates representing the same notification in different languages, it's needed to generate 1 rule for each language in order to respond the Requester in an appropiate way on their language. In our case, with an international sctructure of different departments abroad, it's implying an enormous collection of rules than, in essence doing exactly the same thing but in different languages.
I think would be very useful to develop i18n characteristic on email templates vs rules, as explained:
- 1:N relationship on "1 template…
1 vote -
Tab based system to view tickets
When you click on a ticket to read it, it opens it in a tab at the top of the screen and pauses time tracking for every ticket except the one you are viewing.
This would be useful for comparing information between tickets without having to open multiple browser tabs.
1 vote
- Don't see your idea?