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.
Hey all!
I am thrilled to announce we've launched a separate permission to edit and curate the knowledgebase without needing admin rights.
This comes with an overall UX improvement to the permissions page and new permissions focused on the RMM side of things.
Feel free to read more about the feature here
We hope you enjoy this new release,
Yakov
-
Davis Clark commented
In Atera it requires you to have administrative rights to be able to create a KB. This is a very unusual permission right because it doesn't allow anyone besides having full admin rights in Atera to create a simple KB. A new feature would be nice to add permissions on who can create KBs or view them only.
-
Rupam Sharma commented
Allow Support staff to create KB articles without giving them full admin access. ATM they have to be given Full Admin access for them to have access to Create New Article.
-
Jupo Tayong commented
Would be nice to be able to delegate Atera knowledgebase administration to a technician without giving full admin access.
-
Sara Moss commented
There needs to be a Knowledge Management role for technicians that doesn't require full admin rights, so techs can create and edit articles and share with each other without needed access to the entire platform.
-
EPC Support commented
Permission Ticks for custom roles to be considered
Allow A role to create a Customer
Allow a role to remove a customer
Allow access to all customers With exception/exclusion
Allow to Modify or submission to Knowledgebase (with ability to restore previous version)
Allow to create KB for internal
Allow to create KB For Customer
Allow to create Scripts
Allow full admin - with customized Feature/plugin blocking -
abigael abigael commented
Ability for non-admin technicians to add and edit KB articles
-
Jared Payne commented
As a business owner I don't want to give admin rights to my techs because if I ever have to let them go or they get mad they can't do too much damage. However, I do want them to be able to add articles and edit articles and add sections and all that to the knowledgebase. Documenting fixes and yoru work is a key part to a good tech's work ethic. Currently, we use a different competitor's product for our knowledgebase becasue of this bizarre lack of granular permissions on something so basic.
-
CloudGenie Support commented
Atera engineers need to learn ITIL best practices. How can you not allow a tech to edit KB articles (if company allows) without full admin privileges is beyond me.
-
Stephen Lynch commented
After joining the organisation and finding an empty knowledge base, I asked my team to begin adding their knowledge into new articles, only to find that only full admin users have access to do this.
I would really like this feature to be included and have a toggle for individual users in the same way as the original request. This will allow control over who (at a user level) can actually create articles.
One additional point would be to move the "For Internal Use Only" check box to the top of the new article screen. This will help prevent the forgetting to check for internal use. Alternatively, could we set the default value to be Internal Use Only and have access to that check box limited to Admin only, thus forcing the relevant proof reading for external documents. -
Kamill RACZYNSKI commented
Allow the technician group to create articles in the knowledge center
-
James Harrison commented
I agreee, I had to give a few technicians admin so they could just write knowledge base articles
-
C Masters commented
The ability to add KB articles should be an assignable permission to any defined role. At a minimum, however, it should be assignable to the default Technician role independent of administrator status.
-
Danny Stergiadis commented
The technician roles section needs to separate permissions more.
We need a new permission switch to give techs who are in a specific role to have access to create knowledge base items without giving them full admin access. -
Alex Chmara commented
Allow us to turn off Knowledgebase access (togle on off) under roles for techs.
Also give us the ability to assign "editing/posting" privileges to knowledgebase without full admin.. -
Lee Meade commented
Totally agree, i have created a role for engineers but they cannot add an article wihtout being full admin. This means that only managers can create articles.
THis should be an option in the role permissions section
-
Jason Burris commented
I'd also suggest a toggle for adding/editing a customer.
-
Modular Business Solutions Support commented
I saw in latest release that users can now have device control as well as monage scripts and patches etc without admin permissions but admin permissions are still required to edit knowledgebase.
I would suggest a toggle to allow / disallow access to:
Custom Fields
Ticket Automation Rules
Software Bundles
Thresholds
SNMP Templates
Email Templates
KnowledgebaseThis will make it easier to delegate hman resources to roles without needing to give full admin permissions to edit / create a KB Article.
Thanks.
Mark. -
Paolo Zoglianti commented
Please add the ability to allow technicians with no admin rights to manage KB articles.
I would like to assign one my techs the task to build our KB for clients as well as for Admins.
Also, I think that currently technicians without admin rights are not able to view internal KB articles.