Recent searches
No recent searches
Separate Permissions for Approve and Publish in Guide
Planned
Posted Apr 27, 2021
We really need a mechanism to differentiate publishing permissions vs approving permissions. Our content experts need the ability to approve articles, but not to publish articles. This is because our content experts approve the content of the article, but are not intimately familiar with our publishing requirements and need the extra eyes to help correct spelling/grammar/formatting/etc.
Unfortunately the way Guide is designed now, it’s an all-or-nothing affair – you either get to approve AND publish, or you do not get either of those abilities. These permissions really need to be separated so we can prevent low quality content from being published before it has been QA'd.
16
8
8 comments
Mary Paez
I created a simple differentiation of the permissions that are needed. We would differentiate btwn KCS I, II, and III.
The permissions would look like this at a high level:
5
Jonathan Chellis
@... I like this, but would only grant any ability to publish to what you have as KCS III. Might also be a question of intended audience too - perhaps KCS II could publish articles that are only viewable by your org's agents and not to your end users/customers. This then would turn into a requirement for separate permission sets for who can publish articles with x or y visibility settings, which... also isn't part of Guide.
At least I'm glad I'm not the only one who needs more granular management permissions!
1
Mary Paez
I agree here. Give us the ability to turn on and off the permissions we need to define the KCS Levels we need. :)
1
Kalle Windefalk
Totally agree!
I would like to add the article states "not validated" and "validated" to @... table above. "Archive" is in fact an KCS article state and all of them should be present.
Those article states should also be present in the article fpr all audiences.
2
Mary Paez
I think every time an action is completed, the status change should be updated. However, there is one action that is seems non-functional: Submit for Review. If this action is taken, it should send a notification to the individual that the article is assigned to. The status should be updated to "In Review".
If an article In Review is approved, the status should be updated to "Ready to Publish". If rejected, the status should go back to "Draft - In progress". The statuses should reflect the actual state of an article.
4
GDK
I agree this would be extremely useful.
0
Adam Brown
This is still an issue.... nearly 3 years later!
1
Katarzyna Karpinska
Hey All, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.
This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
Thank you again for your feedback and for being a valuable customer with Zendesk.
0