-
IT Automation
It would be helpful to be able to control what Technicians see and have access to within IT Automation.
∙ A Technician cannot assign an IT Automation to a device or folder unless I turn on the IT Automation feature within the Technicians > Role Assignment.
∙ I don't want my Technicians to view or even be able to select an IT Automation that is not relevant to that particular Customer.
∙ If I enable IT Automation for a Technician, they can see all jobs, and edit all jobs, etc. It would be preferred that they can only view them…1 vote -
More Granular User Control
Expanding on earlier idea would be good to have the following:
In Role Permissions:
Build on to Desktop Remote Management and Server Remote Management but have a new item:
Server Remote Access - Toggle remote access on or off for Servers.This way we can have a tech monitoring servers and running scripts we have made but make the tech assigned to role unable to remote into servers (Think L1 or L2 tech).
Speaking of scripts, before "Manage Scripts" have a toggle to:
"View Scripts" - on and off so that we can assign L1 or L2 tech the ability…2 votes -
Technician Out of Office
It would be great for a tech to be able to set themselves as 'out of office' if they're away for any period of time. This way if a client updates a ticket assigned to that tech we can have an automation rule unassign the ticket so someone else can deal with it.
At present the only way to do this is either, have someone watching that tech's tickets, or unassign jobs before leaving for a holiday/sickness. The process is too manual.
2 votes -
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 -
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 -
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 -
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 -
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.
6 votes -
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 -
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!
-
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!
-
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.
8 votes -
Uploaded or contributed scripts need to be verified
Uploaded scripts need to be verified safe before general release to confirm they are not opening doors to hackers or compromising systems in any way..
2 votes -
Allow technician to pick from others within the same role for ticket assignment.
Rather than requiring "global" ticket access. It would be helpful if the system would allow the assigned technician to reassign the ticket to another tech within the same role/group. Or allow a ticket to be auto-assigned/round-robin to members within a role/group.
1 vote -
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!
-
1 vote
-
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!
-
oauth/oidc support for admin/tech and also customer portal
Add support for oauth/oidc so that it's possible to setup against azure ad for an example. Then neither admin/tech or customers would need to hazzle with yet another password.
1 vote
- Don't see your idea?