Cloning Knowledge Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2026 02:17 PM
Has anyone used the knowledge Center yet? it's like a workspace for knowledge users.
Here is our challenge: we have Tech knowledge admins and HR Knowledge admins.
1. is it possible to have the lists only show data for the personas who opens up the center? like a benefits knowledge manager only sees data fit to their needs? and not expiring or flagged tech articles?
and HR knowledge admin sees what's relevant to them only like HR group approvals
2. or would it be the arduous task of cloning the whole workspace? would anyone recommend that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
We're running into this exact challenge with enterprise customers right now. The short answer is that Knowledge Center doesn't scope the workspace view by KB ownership OOTB — it filters based on what the user has access to via User Criteria, but the UI itself isn't domain-aware. So your Tech and HR admins will both see a blended view of everything their access allows, not a clean "here's your stuff" experience.
Cloning the workspace is technically possible but honestly not worth it for most orgs — it's a maintenance headache across upgrades.
What I've found helpful in the meantime: once you're inside the center, you can use the list filters to scope down to a specific KB. It's a manual step each time, but it at least lets each admin quickly narrow their view without wading through everything else. Pair that with tight User Criteria on each KB and the noise stays manageable.
The KM product team has acknowledged this as a gap and it's on the roadmap, so worth submitting through the Ideas Portal to add some weight to it if you haven't already.
