We regularly collaborate with clients who have their own in-house IT administrators. In these cases, we create dedicated user accounts so th
We regularly collaborate with clients who have their own in-house IT administrators. In these cases, we create dedicated user accounts so they can access only their own customer data within our environment. However, we have noticed that these users currently have full visibility of our entire knowledge base, including internal documentation.
To support secure collaboration, it would be highly beneficial to have more granular permission controls within the knowledge base. Ideally, this would allow:
Restricting access to the knowledge base on a per-user or per-role basis
Limiting visibility to specific folders or articles
Marking certain knowledge base sections as internal-only
This functionality would enable us to collaborate more effectively with external IT administrators while ensuring that internal documentation remains protected. We believe this would not only benefit our organization but also other MSPs working with co-managed IT environments.
Jeroen Van den Boogaart
shared this idea
Hi,
Thank you for your valuable suggestion. While we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
We continuously review user feedback to inform our development priorities, so your idea remains on our radar.
Best regards,
The Atera Team