KB Review/Expiration
M
Matt L.
I would like to see that when a KB is created is goes through an approval process. I would like my team to be able to create KB articles as they go be want to be careful they are useful.
I would also then like to have a expiration policy that applies to articles so they can be reviewed, updated or removed. That way old data isn't staying in the system and not helping.
P
Paul H.
Also a requirement for us - ISO27001
Kristen W.
Merged in a post:
Review workflow for new/edited KB articles
Frans van 't Hek
To conform to ISO27001 standards we require newly created or edited KB Articles to go through an approval process.
Currently we have no way of creating a workflow for review and approval/decline of newly created or edited KB Articles.
A simple feature to automatically tag an article as “review neccesary” with a notification sent to a certain group of users (HUDU Admins) would suffice.
Please consider including this feature in your product, since there are most likely other companies using your platform in need of this feature.
W
Will Kochis
We've been with Hudu for some time and KB or article management has become untenable. We need everyone to be able to submit articles that go through an approval process. We need flagged articles to go back to a queue where they can be unpublished until the approval reviews.
N
Netcare S.
I agree. Would also be good to categorise KB articles. Plus have a review date say defaulting to 12 months etc.
J
Justin S.
This is also mentioned on Feature Request https://docs.mycompassonline.com/feedback/p/kb-reviewexpiration
I've added my vote to both this Feature Request and that one.
J
Justin S.
Just want to add my vote to this feature request. Everything mentioned so far are all important aspects of the KB IMHO:
- Expiration dates so we remember to review certain items with a certain amount of regularity.
- The ability for people to create / edit KBs with those changes only being a "suggestion" that needs to go to an approver before it's published.
- Make #2 above auditable.
Frans van 't Hek
We need this feature to conform to our ISO standards. Currently we have no way to create a workflow for review/approval of documentation, which makes it so that we have to restrict what users within the company are able to create articles in HUDU.
A simple workflow to notify "KB Admins" to review newly created articles, and either approve or decline them, would be sufficient.
P
Pieter W.
this is becomming a serious requirment. Our ISO27001 auditor fail us, on not having a auditable approval proces in place on the HUDU KB.
Great if this can be picked up quickly.
Simple flow, either approved an published or decliend and returned to editor .
Both with a logged comment
N
Nicholas P.
This is a Big thing. Most documentation storage platforms have something like this. It would allow all users to submit documentation but only certain users could approve it before publication.