- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2017 11:43 AM
We have finally started working on Knowledge Management. I have found an OOB issue with permission levels according to editing KB articles.
We have our KB broken up into our various KB categories including Security, Signage, Housekeeping, Maintenance and Construction. There are various articles within the categories that I would like to restrict editing. By default everyone can edit who has a role. I don't want to set the role permissions at the Knowledge Base level with Can Contribute, because I need further access control at the article level.
I have created a new choice list field on the knowledge article form called Facility Department (u_facility_department).
The goal is to allow only certain roles to edit certain KB articles.
For Example:
A maintenance manager can only edit articles related to maintenance which are categorized using the "Facility Department" choice list field, u_facility_department. A housekeeping manager can only edit housekeeping articles, a construction manager can only edit construction articles, etc.
I would have thought that whomever the Author of the article is would be the only person other than a knowledge_admin or admin, who could edit the knowledge article, but this isn't the case.
I'm not sure where to start or a script that might work, but where would the script go?
Thanks in advance!
Solved! Go to Solution.
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2017 05:53 AM
I'm trying to find something very similar. The challenge with ACL level is that OOB ACLs already exist. That means the role is going to give permissions unless you deactivate that OOB ACL, which you don't want to do.
Business Rule Option
An option that would definitely work is to use a before Business Rule on update. It would check the user and the Facility Department. You can abort the action so the record does not save current.setAbortAction(true). You'd probably want to show an info message as well. You may want to do a display BR as well to show an Info message to the user that they will not be able to edit.
UI Policy
Write a script condition on a UI Policy for your Knowledge form. It can make all of the fields read only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2022 10:59 PM
Hi Gregg,
Can you please provide the script for BR, it would be helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2024 08:29 AM
I have this exact same issue and even though this post is 6 years old, can you share what ultimately worked for you?