The Expanded Permissions feature allows admins to restrict access to different components within Level. Some ideas: Read-only access Removing specific components (remote control, automations, etc) End-user account that only has access to a single agent. See https://feedback.level.io/p/end-user-access
Follow this request to get an email when its roadmap stage changes.
5 comments
Use the email address associated with your Level account.
We urgently need this in Europe for customers with special security requirements.
We also really could use this. We will have lower level technicians whose abilities we will want to restrict, and more immediately we have clients where on-site contacts get limited read-only access to our RMM. They can see hardware and software details, and take control of devices, but other information and functions are hidden or disabled. There doesn't seem to be a way to allow our clients into Level without also providing them the ability to edit and run features that we can't allow them to access.
+1 for this feature. We were planning on moving to Level from Splashtop for remote access, but without more granular controls for user access we're going to have to rethink our transition.
We need to enable access for customers (now) within co-managed managed services and need this urgently.
The Tech role currently has the ability to edit and delete Policies and Tags, which poses a significant risk. This should be addressed as a priority. Thanks
