- or
No existing idea results
- ~ No ideas found ~
4973 results found
-
Notes in app
A way to add notes to a customer in the mobile app.
6 votes -
Allow Linux computers the ability to be a monitoring agent for SNMP, Network Discovery, etc. devices?
We would like to put our own linux system at a users site to monitor SNMP instead of relying one of the clients systems.
3 votes -
Two Way SplashTop Audio
I got a request for two way audio via the splashtop app.
1 vote -
Webroot actions appear in recent processes
When deploying webroot via the atera option there is no record for that action under recent processes.
I could get a record if running it as an independent script but that feels pointless when it's built into Atera4 votes -
Assign multiple technicians to a ticket
By a community member:
We need the ability to assign multiple technicians to a ticket. We have ceveral tickets that would consider projects requiring multiple technicians to coordinate assigned tickets.392 votesHey all,
We're excited to announce that we're exploring the development of a new feature focused on ticket queues and assigning technician groups in Atera.
Your feedback will be invaluable as we shape this feature to meet your needs and preferences.
If you'd like to provide input on this feature, please schedule some time for a call using the link below:
Your insights and suggestions are essential to us as we continue to improve and innovate within Atera.
All the best,
Yakov
-
System shutdowns should either report under the "Last Reboot Time" or in their own category.
I was told they are not the same, but it is basically the same. You want to know when the system was rebooted/shutdown. I had a client that hadn't rebooted, but they shutdown their machine every night. The system reports this as uptime, which is very wrong.
2 votes -
Provide the ability to run a report with all customers selected
I would like to run a report for all customers selected at once. Then have the ability to export as a .csv file so I can analysis the data to figure out what we have in the field.
2 votes -
Add subscription renewal date to subscription page
It would be helpful to know when our next subscription billing date is on the subscription page itself. Right now it just shows Monthly and Yearly fee along with payment info. I had to contact support to see when my next billing date would be.
2 votes -
Change Activity Status as an action for the ticket automation rules
Change Activity Status as an action for the ticket automation rules
2 votes -
Change email response when "Login using activation link" is clicked
The email sent is unbranded and looks suspicious.
It would be good to create our own branded email and provide further information such has details on how to log a ticket correctly1 vote -
Tickets from Alerts auto-requestor-assignment
If there is no user assigned to a "machine causing an alert", set "requestor" to a Techician or System.
Current automatic behaviour is to set the first (alphabetically) contact from the affected Site to the alert/ticket .1 vote -
tag search
Adding tags to different tickets are not getting recognized by the search engine.
It would be great if you can search for ticket-tags just like in the knowledge base with "#tagname" or if there is a free-text field in the filter section and not just checkboxes for the tags.
And on top of that in the filter section the tags are not in alphabetical order, this would help too!greetings
2 votes -
Integration with supremo
Integration with Supremo (as team viewer)
6 votes -
Alert For Expiry Date In Assets
Alert options for expiry dates added to assets.
3 votes -
usecure
usecure.io integration https://www.usecure.io/
1 vote -
Add "Requires Reboot" to Atera API
At the moment, the Atera UI shows us that a machine requires a reboot, but without running a command against each machine, it is not possible to identify if they require a reboot directly with the API. This would be a very useful feature for the purpose of patching and reporting.
9 votes -
datto
Integration into Datto backup and Kaseya spanning would be a nice to have. Not critical.
8 votes -
Add option for app-based 2FA for Work from Home (instead of only via SMS)
2FA Authenticator app for work from home instead of just 2FA via SMS
Right now, work from home only facilitates 2FA through the use of SMS. It would be nice to see the option to enable 2FA through the use of a 2FA app such as Duo, Authy, Google Authenticator, etc. This functionality is already available for technician accounts.Technically, 2FA via SMS is the least secure method of doing 2FA and it has been demonstrated that a sufficiently skilled hacker can intercept the text messages that contain 2FA codes. For this reason, app-based 2FA is preferrable over SMS-based 2FA.
SMS-based 2FA is still desirable to some people, so it is probably useful to keep it as an option, but having an option to use app-based 2FA would be appropriate from a standpoint of security posture.
2FA Authenticator app for work from home instead of just 2FA via SMS
Right now, work from home only facilitates 2FA through the use of SMS. It would be nice to see the option to enable 2FA through the use of a 2FA app such as Duo, Authy, Google Authenticator, etc. This functionality is already available for technician accounts.Technically, 2FA via SMS is the least secure method of doing 2FA and it has been demonstrated that a sufficiently skilled hacker can intercept the text messages that contain 2FA codes. For this reason, app-based 2FA is preferrable over SMS-based 2FA.
…
36 votes -
Tickets are duplicating due to Subject line
Instead of checking the Subject line to prevent tickets being duplicated, instead insert a ticket ID into the body and check for that ticket ID in the body to prevent tickets from duplicating due to replies not having a specific subject.
Cherwell does this, it places the ticket ID into the body, For example, within the body, you'll find the Ticket ID written out on the bottom of an email - {CMI 43EF84993H2}
Cherwell scans each email's body for the ID and places/groups that email into the correct ticket. If it doesn't contain the ID within the thread of emails, it generates a new ticket. If the ID is so old and resolved, it creates a new ticket.
Why I bring this up is because Atera tickets are duplicating whenever someone alters the subject line with either a "RE:" or a "FWD:"
Atera depends on the subject being identical to the first subject line that initiated the email OR keep the ticket # in there, which is only generated if the ticket has been responded to, when you respond within Atera, it adds "Ticket # 1234" to the subject line.Issue with changing the subject is that it creates a new thread for the end user, which is a bad practice because end user also wants the email to be under one email, and not two separate emails.
Instead of checking the Subject line to prevent tickets being duplicated, instead insert a ticket ID into the body and check for that ticket ID in the body to prevent tickets from duplicating due to replies not having a specific subject.
Cherwell does this, it places the ticket ID into the body, For example, within the body, you'll find the Ticket ID written out on the bottom of an email - {CMI 43EF84993H2}
Cherwell scans each email's body for the ID and places/groups that email into the correct ticket. If it doesn't contain the ID within the thread of emails,…
1 vote -
Atera Back up
Backing up or exporting files: We spend all of our lives backing up things for our customers, feels uncomfortable not to back up our databased. if Atera is hacked and if we don't have a back up and we will have a problem. It would be a facility to have a backup of Atera. It is not about migrating to a new service. Us knowing we have a secure backup every week and every night.
63 votes
- Don't see your idea?