- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2019 05:17 AM
We have a requirement that when a person creates Knowledge article named 'Read Access to Managers' under knowledge base 'Business Work Procedures' then the knowledge article should be visible & read only by the members in the group 'Managers' .
If a person creates Knowledge article named 'Work Manual for Employees' then the supposedly created KB article should be visible to all End Users .
I think the user criteria might not work as the requirement depends on the option the KB article author chooses .
I am thinking that to put two check boxes on the KB article form 'for mangers' & 'for employees' .
if the user chooses the check box 'for mangers' then once the KB article is written & published should be visible to only the members of the group 'Managers'
if the user chooses the check box 'for employees' then the KB article which is being written should be visible to all end users once published .
I am guessing that ACL's might work but i am not having good practice of writing ACL's . any approach of ACL's script would be utmost helpful .
If there is any other way to do so requesting to guide me further
Solved! Go to Solution.
- Labels:
-
Knowledge Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2019 07:43 AM
There are two options where you can control who has access to knowledge articles.
On a per article basis you can set it via role, in this case you would have to create or use two existing role, if an article is to be accessible to all employees then you can omit this one, leaving it blank would allow access to anyone who has access to that knowledge base.
You would have to setup a role for managers, add all your managers to it then assign this role to the articles you wish to restrict to managers only (this will require you to go in to each article and add the role)
The other alternative is to setup a second knowledge base, at a knowledge base level you have more granular controls as to who has access (permissions can be set via user criteria using: role, individual users, groups, companies, locations, departments).
What you would have to do in this case is move each article for managers only in to this knowledge base (so both options would require some manual effort)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2019 06:12 AM
Why would you just not have two different knowledge bases? They you can use user criteria to set who can read and who can contribute.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2019 06:32 AM
How do you even tell if someone is a manager or employee?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2019 04:25 AM
Mangers are in the group 'Managers' & all other end users are employes

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2019 07:43 AM
There are two options where you can control who has access to knowledge articles.
On a per article basis you can set it via role, in this case you would have to create or use two existing role, if an article is to be accessible to all employees then you can omit this one, leaving it blank would allow access to anyone who has access to that knowledge base.
You would have to setup a role for managers, add all your managers to it then assign this role to the articles you wish to restrict to managers only (this will require you to go in to each article and add the role)
The other alternative is to setup a second knowledge base, at a knowledge base level you have more granular controls as to who has access (permissions can be set via user criteria using: role, individual users, groups, companies, locations, departments).
What you would have to do in this case is move each article for managers only in to this knowledge base (so both options would require some manual effort)