Is there an OOTB way to control who can view sections of a knowledge article?

[Taylor20]

Hi all, 

Is there a way to ensure specific sections of articles in a knowledge base available to several groups can only be viewed by one group? 

I'm looking at ways we can improve our knowledge articles and a lot of them could have extra information added that only our Security Team would need to see (other than knowledge managers and admin of course). 

If there isn't an OOTB solution, has anyone found any ways of implementing this approach? 

Thanks,
Taylor

[Swapna Abburi]

@Taylor20 
I don’t think so content level restriction is available in articles. However, you can restrict individual articles by using can read and cannot read fields on articles. 

if you have additional content which you want to display it to limited audience, I suggest you create another article along with addl content and restrict article using can read and cannot read fields available on article ootb. 

[Lauren Methena]

Knowledge blocks typically act almost identically as knowledge articles, so much of what you can do to articles, you can do to blocks. Examples: You can apply CAN READ criteria to limit visibility to select audiences. You can attach documents to them the way you would an article. Formatting, anchor tags, etc., are all possible in a knowledge block.

Hope this helps! 

[Community Alums · Accepted solution]

Hi @Taylor20 ,

You have multiple options:

1) Use Knowledge Blocks 
2) 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;

3) 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.

4) 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.

[Community Alums]

Hi @Taylor20 ,