HR Articles that need Legal to Review
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
13 hours ago
Hi All,
If there are certain HR articles that need the legal team to review them (i.e. Leave of Absence) vs. for example, Facilities which does not need a legal review, how would you set that up? I'm thinking the following:
1. An HR knowledge base where when the author hits publish, the legal team will get a notification to review and once they approve it will then come to the KM team to review to make sure it meets the style guide/article approval checklist.
2. Another HR knowledge base where once the author hits publish, it just goes to the KM team to review to make sure it meets the style guide/article approval checklist.
Is that the best method? Any other suggestions? I could name them something like HR (with legal review) and HR (No legal review). Something like that. Any suggestions/advice is greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
I would keep this as a single HR knowledge base unless there is a separate audience, access, ownership, or lifecycle requirement that justifies a second KB.
The publish process is configured at the knowledge-base level, so I would create one custom publish flow for the HR KB and add conditional routing within the flow:
-
Articles requiring legal review: Legal approval → KM approval → Publish
-
All other articles: KM approval → Publish
I would recommend using a dedicated field such as Requires legal review rather than relying solely on category. Categories are helpful for organizing and finding content, but the legal-review requirement may eventually apply to selected articles across multiple categories.
If the Knowledge Management KCS Capabilities plugin is active, the Governance field may also be worth evaluating. It distinguishes experience-based articles from compliance-based articles, such as policy or legal content that requires tighter control.
Separate KBs would be more appropriate if the articles require genuinely different access controls, contributor groups, owners, or lifecycle rules—not only a different approval path.