56 results found
-
Role to allow customer creation for st line technicians
The ability for a role to allow customer creation. for example 1st liner technician needs to be able to assign contacts and companies to a new ticket and request. as of right now this CANT be done without giving FULL admin access to a role.
It would be very helpful for new contacts to be able to be linked to a new company name. Without a company name they are stuck on unassigned which affects the reporting side of things.1 vote -
Record remote session and save it on cloud storage for auditing.
It would be great if we can enable the recording for remote session permanently and save the video on the cloud storage safely for auditing purposes. I know any desk has this recording feature, but the video gets saved on local computer where technician can delete or modify the video file. So, my suggestion is setting up integration with Cloud storage such as “Wasabi Cloud storage” and Any desk or Splashtop to save the video on the cloud. Wasabi provide very inexpensive cloud storage $6 for 1TB.
5 votes -
remove technician
Ability to fully remove a technician, not just disable the account, to keep the user list neat and tidy.
21 votes -
Remove contract view from technicians
When removing permission for a tech to see billing, it should remove the possibility for them to view contracts and being able to edit them as well.
5 votes -
Hide Technicians
Role and permission: I want to provide a license for my client. I can limit his access on the platform. However, the client can still see all of the technicians that are one my account. I don’t want my customer to see all my technicians under my account. I don’t want my client to then contact my own technicians
2 votes -
Remove View Script options for technicians
Ability to remove "view" option for scripts for tech that are not admin - Currently when they run the script on a device, there is option to view the script. The use case for that is, if we are using API key in the script to use custom fields, we don't want to expose our API key to normal technicians.
14 votesHello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
-
Restrict technicians to some customer folders only
To assign a technician to give permission to certain folder and not everything. Restriction based on departments and not “sites”
9 votesHello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
-
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…3 votes -
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…26 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.
14 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.
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 them12 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.
6 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.
9 votes -
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.
3 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
5 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.
50 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.
38 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$33 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.
9 votes
- Don't see your idea?