Skip to content

Knowledge Base Governance

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Scope

Admin controls for assigning and removing Knowledge Base owners and managers, used by a System Admin to establish clear accountability for each body of policy content across multi-team organizations. Delivered through the Policy List Service Portal widget's KB-management view.

Value

Without defined ownership, nobody is accountable when a policy article goes stale. This closes that gap — every KB has a named owner/manager a reviewer or auditor can point to.

Acceptance criteria

  • A System Admin can open KB management in the Policy List widget and assign or remove a KB manager for a given Knowledge Base.
  • Assigning/removing a manager updates kb_knowledge_base ownership/manager records (or this Feature Set's schema delta, per ../schema-changes.md, if OOB fields prove insufficient).
  • Accountability for a given body of policy content is visible to anyone reviewing KB governance — not just to the admin who made the assignment.
  • Manager assignment made here is consistent with, and visible from, the in-editor manager assignment described in ../native-policy-editor-collaborative-authoring/spec.md — the two entry points (admin console vs. in-editor, for new policies) write to the same underlying record rather than diverging.