58 results found
-
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
161 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!
129 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.
44 votes -
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$35 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…
35 votes -
Free Account User for Admin Purposes
I gather it won’t happen everywhere but certainly happens at our end (and most companies I work with); but we employ an accounts lady who handles all purchase ledger invoicing (buying a pen, paying for the supply of gas or electricity but also for Office365 or AWS) which is mostly done via our business partners portals.
So basically one (free of charge) account should be made available per company that strictly covers administrative duties limited to Atera subscriptions and licensing, add and remove agents’ licences, edit payment details such as credit card details, invoices, etc.31 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.
31 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…28 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.
23 votes -
Separate File Transfer permission
I do not want any Admin or technician having access to the files and folders of an end-user. So either this "File Transfer" option should be configurable under Permission-Roles or there should be granular permissions for the "Desktop Remote Manage" permission under RMM in Roles. I wouldn't mind this feature to be totally disabled as this can raise a flag in security audits or can cause a management concern where security of data is of topmost priority.
18 votes -
Ticketing only Atera license
Ticketing only Atera license
16 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 votes -
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.14 votes -
Technician Role permissions
Roles within Admin need to have the ability to have more control of what features each group has.
Under RMM, the "Edit Device" feature is too strict. We want to be able to allow certain technicians to edit device names but not be able to delete them.Setting that can be turned off so that no technicians have the ability to delete anything.
12 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 -
Option to remove Add-on Tabs
Ability to give the option to hide the Add-ons tab
12 votes -
For roles and permission: ability to create groups of technicians and then assign those groups to the customer
For roles and permission: ability to create groups of technicians and then assign those groups to the customer so they can have access to the clients. As soon as you add a new technician to a group, that technician will then have access to X client. As of right now, if we create a new customer, we then need to go to each technician and give them that access. It can take a long time. A lot of our technician have a different role each.
10 votes -
Help Desk Administrator
Atera should have additional billable (or free...) roles other than technicians. We have project managers & help desk admins that do not provide technical support.
We don't use Atera's ticketing because our admin staff would cost us an extra $300/month just for them use the help desk, nothing else.
We would love a discounted "role" of a "Help Desk Manager" who like a technician has granular access to help desk tickets per assigned client. But that's all they can do.
We have someone that can manage tickets, assign tickets, but do not have to be a full $150/month agent since…
10 votes -
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”
10 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.
10 votes
- Don't see your idea?