Restricting Users to Article creation in one knowledge base

[aguanci]

Hi All, 

Currently we have 2 Knowledge Bases:

• Human Resources General Knowledge
• HR Analyst Knowledge

The Human Resources General Knowledge only allows for 8 users to create articles for the whole Knowledge Base. 

For the HR Analyst Knowledge Base we have been asked to give those same 8 users plus some additional users the ability to create articles for that knowledge base only. 

Is there a way to restrict the additional users to only have the ability to create articles for the HR Analyst Knowledge Base? 

[Mike Wood]

Hello, 

I have not experienced that issue. It sounds like there could be a permission issue.  Do you have the Knowledge Admin role ?  If not, you would need that role unless someone has setup a different ACL with those permissions.

[harivats]

There are two ways

- one at the knowledge base level

- one at the knowledge article level

If you want to restrict the knowledge base level - create a user group and add those required people to that group and it will be restricted

if you want to restrict the knowledge article to only those 8 users - again create a user criteria - add those user criteria to can contribute which will help those users to contribute to that knowledge base. For the article level make sure this property is activated - Glide.knowman.apply_article_read_criteria which will override contribute access to knowledge article based on can read and can contribute at the article level. 

[Sumanth16]

Hi @aguanci ,

You have multiple options:

1) Create a specific Knowledge base that will be used only to store those articles realted with business continuity. You can then create a User Criteria to grant read permissions on that knowledge base to users belonging to a specific group;

2) Put the articles in the same knowledge as other articles and manage the Can Read field. You mentioned that your customer does not like this solution, but it is a fairly easy and secure way to manage the access to specific records.

3) Create a specific read ACL that will restrict read permissions on articles from a specific category for a specific group.
NOTE: setting up ACLs with user criteria can end up with strange behaviors. Avoid using ACLs with usage records.

If I was the one choosing, I would go for option 1.
in option 1 you select the users that will have access to the entire knowledge base. That gives a very good level of protection/security and at the same time creates a logical separation from other knowledge bases.

Please, don't forget to mark my answer as correct if it solves your issue or mark it as helpful if it is relevant for you!

Thanks & Regards,

Sumanth Meda