- or
No existing idea results
- ~ No ideas found ~
5083 results found
-
Create contacts and tickets from end-user calls
Enable IP telecom data (incoming calls from end-users) input to create contacts and tickets
1 vote -
Add requester fiedld to tickets view
There is no way to filter ticket by specific requester.
I have a chat with support to confirm that.
It will be very helpful if you add a requester filter to tickets view1 vote -
Make the fields Priority, impact and type empty
The Priority, impact and type are now filed in, but it should be empty, so a technician is required to fill the with the correct fields. Now the default always are
Low, no impact and incident. This means nobody thinks about it and use these fields2 votes -
new feature request
I would like to have the ability to set each customer's remote preference as Attended or Unattended. This would be ideal for different customer types.
2 votes -
Scheduled Tickets Filter or Search Option
It would be nice to add a feature to filter or search through existing scheduled tickets. We have 100s of scheduled tickets to modify a ticket it can be a pain to dig through
9 votes -
Cloudradial
I would like Atera to integrate with Cloudradial. And very soon, otherwise we have to look at Syncromsp as a new rmm
3 votes -
Connectwise Importer
An Import tool for Connectwise Manage to pull information into Atera. for record history and to keep clients information up to date after a migration from CW Manage to Atera.
4 votes -
Device Events
I would like to see device events as detected by Atera for individual endpoints. I recently had a client rename an endpoint which caused some duplicate entries in some of the other platforms I use. Atera kept working just fine, but it would be really nice to see a history of events like this so I can see what happened and when.
There are several other use cases where this would be really helpful too:
1.) Script executions
2.) User account creation
3.) User logon/logoff events
4.) Critical/Error event log entries
5.) Shutdown/Startup events
6.) Windows Updates (client native, Atera managed, Automation Policy, and ad-hoc)
7.) Software install/uninstall events
8.) Ticket statuses (create, resolved, closed are all that's really necessary here)All of these should be viewable when on the device page itself. I posted a similar request here: https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/45007048-device-activity
I would like to see device events as detected by Atera for individual endpoints. I recently had a client rename an endpoint which caused some duplicate entries in some of the other platforms I use. Atera kept working just fine, but it would be really nice to see a history of events like this so I can see what happened and when.
There are several other use cases where this would be really helpful too:
1.) Script executions
2.) User account creation
3.) User logon/logoff events
4.) Critical/Error event log entries
5.) Shutdown/Startup events
6.) Windows Updates (client native, Atera…4 votes -
Generate Detailed Event Viewer Reports
It would be good to be able to generate reports based on specific Event Viewer events and IDs, along with details about the events. Currently we can monitor for the events, but we cannot see any details about any events in a report format.
4 votes -
Auto-Deploy AteraAgent via Scheduled Scan
Network Discovery: Auto-Deploy AteraAgent if not detected on machine.
Configure at customer/domain level and schedule your scan. If AteraAgent is not detected it is installed (laptop, server, desktop, etc).
27 votes -
Data Export
Provide the ability to export client data such as passwords and other important information so it can be stored securely offline in the case of Atera not being accessible.
5 votes -
Configure Splashtop and Anydesk audio settings during remote sessions
Add the option to disable audio from remote computer during remote sessions. In splashtop and anydesk.
21 votes -
physical age of device report
It would be nice to have a report that would show us the physical age of a device, this would allow us to be able to state to a Customers/Client. That because your machine is X years old, we recommend upgrading or even replacing the device, because we are finding a trend that the older a device is the more tickets that device generates. Also a faulty machine that is always generating tickets is not good for the customer's work flow.
18 votes -
Agent Install Location
Suggesting we change the default install location for Atera agent and all remote tools to these path.
• C:\Program Files\X\ATERA Networks
• C:\Program Files (x86)\X\Splashtop
• C:\Program Files (x86)\X\ScreenConnect Client (b7d7eaa43a30baba)
• C:\Program Files (x86)\X\AnyDesk-f45e5af2_msi3 votes -
Adding Category Type to Password Manager
I would like an option to add additional Category Types in the Password Manager.
4 votes -
CPU Temperature in Metrics
I would like to see CPU temperature history in the metrics to pinpoint and correlate activity with temperature.
52 votes -
Ad reset and unlock account
often need to reset and or lock/unlock AD user account.
A module to connecto to AD would make it so practical.Disable account
Reset Password
enable expiration
require password change
Member53 votes -
non tech role
Desperately need various roles for non-technical people to be able to access Atera for PSA and Billing purposes.
Sales people should be able to add customers/customer information, but never be allowed access to RMM functions like devices or scripts or anything technical--but the option to grant those permissions should also be there for technical-minded sales people. (Think Sales Engineer who moved to that role from Field Tech and helps clear ticket queues from time to time)
Billing people should be able to add/edit customers, do invoicing, manage ticket information (like correcting spelling errors) etc... but not have access to anything RMM.
Desperately need various roles for non-technical people to be able to access Atera for PSA and Billing purposes.
Sales people should be able to add customers/customer information, but never be allowed access to RMM functions like devices or scripts or anything technical--but the option to grant those permissions should also be there for technical-minded sales people. (Think Sales Engineer who moved to that role from Field Tech and helps clear ticket queues from time to time)
Billing people should be able to add/edit customers, do invoicing, manage ticket information (like correcting spelling errors) etc... but not have access to anything…
36 votes -
Password access in the portal
Allow customers to access their own passwords. I.e. Log into the portal to access their email password if forgotten.
43 votes -
Size of patch is incorrect / misleading
Patch management is displaying the Maximum size of the patch, which is completely useless. I'd rather see the acutal size (like in MS catalog)
1 vote
- Don't see your idea?