-
Atera End-User License
You provide a limited license to your customer for the purposes of enabling some level of IT support or support assistance such as tracking and prioritization
128 votes -
Role management
How are you using the Roles' functionality? Would you like us to add any new permissions? Would you like us to add any default roles? Share your needs...we're listening!
84 votes -
Granular User Permissions (Client Folder for example)
More granular user permissions. A lot of things now require the highest admin rights which should really be reserved for the owner. Also, it would be nice if the folders for client devices allowed granular permissions, that way certain techs could have access to some client devices but not all.
10 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
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…
16 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Technician Privileges
Not all technicians should have the same privileges per customer, folder, or machine.
We need the ability to limit level 1 or outsourced technicians from running scripts, accessing a remote command prompt or PowerShell.
Currently, all technicians have SYSTEM account access to all endpoints.
This is a major security concern!
Currently, any technician can reset or create admin credentials.
This includes Active Directory domain controllers.
Entering the following commands from a remote command prompt will grant all technicians domain admin rights.
net user administrator /active:yes
net user administrator $NewPassword$11 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Separate permissions to edit the knowledge base
I think it would be good if there were separate permissions to edit the knowledge base without being a full administrator. A process description does not have to open up the possibilities in the same way as the right to extend a license.
5 votes -
Be able to hide tabs (Work from home, Network Discovery, Get rewards)
I think it would be a good idea to be able to hide these tabs for certain roles
EG we have a client that has an onsite technician and he has access to our ticketing system I do not want him to be able to see those tabs
Our L1 techs should also not be able to see those tabs since we do not use them2 votes -
Activity Log
Ability to set roles for viewing the Activity Log instead of providing full admin access or not. Currently if a user is not granted full admin access, they will not be able to view the activity log.
2 votes -
non technical staff
Need the ability to have non-technical staff in Atera's Admin section for billing and account (customer) setup. These back-office people have zero need nor should they have access to RMM capabilities.
10 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Seperate Licensing management
We would like to have the ability to assign different licensing to different employees as an example if we have a security team to do some port checking or so we would like to assign them the network discovery option but not for the rest of the team that will never use it. This goes for Guest as well for example: Customer would lik to use our tool to jump on his own machines so we should be able to assign a limited license for remote management only.
1 vote -
Ability for techs that don't have Admin privileges to add SNMP
Ability for techs that don't have Admin privileges to add SNMP devices.
6 votes -
The ability to allow end customers to see their devices and alerts in addition to tickets
In addition to a customer portal to view tickets, a non-technician licence which would allow end customers to see their devices and alerts as well
2 votes -
Option to remove Add-on Tabs
Ability to give the option to hide the Add-ons tab
9 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Separate permissions for creating New Clients
A separate permission that we can turn on/off to allow members of a Role to create new clients. I am not comfortable with the idea of allowing all of our technicians Full Admin Access just to have the ability to create a new client/customer.
1 vote -
Centralised User Directory for Technicians:
Centralised User Directory for Technicians: I onboard and offboard talent, I am having to go to the Atera site to manage technicians instead of going to a centralized user directory where I can deprecate users.
1 vote -
Ticket Automation: auto-assignment
For the Admin role the default for:
Ticketing Automated Assignment should be set to
DO NOT Include user in the auto-assignment list found in Ticket Automation Rules
With the option to change the setting without having to create a new role.
HR, Accounting, Owners, NOC, and Escalation need higher-level access without being auto-assigned tickets that should be going to the helpdesk.3 votes -
Permission Levels
Provide more permission to users.
Give permission to assign to folders to not just admin, permission to create IT automation too.6 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
A no-technician-license access for a personal assistant to create or re-assign tickets
A username and password for a PA with no access to reports, devices or alerts.
All that should be available is the tickets section - create tickets on behalf of customers when the PA picks up the phone, ability to re-assign tickets from one engineer to another.7 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
4 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Automatic admin credentials generated for servers that cycle say every 10 minutes
Automatic admin credentials generated for servers that cycle say every 10 minutes.
I know we have this in Connect wise continuum at my current day job.
When we go to sign in to a server we generate a new unique password every time. This password refreshes every 10 minutes or so. This would be helpful for security purposes.
5 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
- Don't see your idea?