Knowledge Management Permission Sets for Knowledge articles and workflow

Problem Statement

We currently do not have permission sets set for anyone for knowledge Management and KCS.

What is the problem?

We do not have a defined set of knowledge permissions. We do not want "Everyone" (Support Engineers, Managers, others) to be able to publish articles without review.

Why is this a problem?

We need to have every support engineer create and modify knowledge articles. We also want a very specific set of users to be able to Review articles as well as Publish the knowledge articles. This will help us build our knowledge and workflows

Proposal

We (GitLab) can define the permissions for Knowledge. By Creating permission sets we can get the workflow properly set up, have support engineers be able to create knowledge as well as modify. We need Reviewers/Publishers to also be engaged so we create consistency and accuracy within our knowledge articles

  1. Administrators (Top Level)
  2. Knowledge Creators (all Support Engineers) Knowledge Modifiers (all Support Engineers)
  3. Reviewers (Currently Iris, Wei-Meng) - need to adopt more team members that can review articles Publishers (Should be a limited role. Once reviewed article should be Published - to Knowledge page)

DRI

@KirstyAllen

Required Resources

Potential Roadblocks/Things to consider

Knowledge workflow. #6660 (closed)

Desired Outcome

Permissions sets - as shown in the graphic

What does success look like?

streamlined permissions

How do we measure success?

Where would future feedback go?

Related Issues/MRs/Epics/Tickets


Edited by Kirsty Allen