Help center Core configuration Knowledge base Configure article review groups Updated Thursday, October 29, 2026 · Marc Staine Review groups connect eligible article submitters with the people responsible for reviewing their work. Team, agent and asset filters help make the review path relevant to the documentation being submitted. Applies to: Supportbench Core. Location: Settings → Knowledge Base → Review groups. Editing requires Administer article review groups. Before you begin You need Administer article review groups and an agreed knowledge-review process.Identify eligible submitters and reviewers, including relevant Teams, Agents, Asset Categories and Assets. A group definition does not grant every author direct publication permission.Reopen the saved result and test a representative consuming workflow. A successful save alone does not verify every reader, assignment or rendered result. Configure and verify Open Settings → Knowledge Base → Review groups and choose New Group or open the intended group.Enter Name/Description and review Active.Configure the submitter filters using the appropriate Teams, Agents, Asset Categories and Assets.Under Will be reviewed by, choose the appropriate reviewer filters. Review both sides of the process instead of assuming every member can submit and review.Choose Save Changes and reopen the group. Check all intended selections.Use a controlled article submitted through the normal review workflow. Confirm the intended reviewer can act and an excluded reviewer cannot, then complete the approved publication route. Settings reference Settings and actionsSettingWhat it controlsHow to chooseName / DescriptionGroup identity and explanation, up to 50/250 characters.Name the review responsibility clearly.Submitter Teams / AgentsPeople eligible to submit through the group.Choose the smallest useful authoring audience.Submitter Asset categories / AssetsAsset-based submitter scope.Use when review eligibility depends on a product or asset.Reviewer Teams / AgentsPeople responsible for review.Choose a maintained group with clear coverage.Reviewer Asset categories / AssetsAsset-based reviewer scope.Check that intended reviewers match the selected context.ActiveControls whether the group is available.Keep active groups staffed and retire obsolete review routes.AuditCreation and update details.Use to trace a recent routing change. Behavior to knowIf a group is missing, check Active, submitter/reviewer scope, and the relevant team/asset relationships. Access to Settings alone does not grant publishing permission. Recommended use Use reviewers who can validate the procedure and its customer audience.Keep submitter eligibility and reviewer responsibility distinct.Review group coverage when teams or supported assets change. Worked example: route a product article from its authors to technical reviewers A controller-support team authors troubleshooting content, while a product-specialist team checks technical accuracy. Create a clearly named review group using the actual configured teams; these examples do not create or grant team membership.Under the submitter filters, select the intended author team or agents. Under Will be reviewed by, select the appropriate technical reviewers. Review both sides separately: a person who submits content is not automatically its reviewer.Add Asset Categories or Assets only if eligibility should depend on that product context. Broad or irrelevant asset choices can make the group apply differently from the intended author/reviewer responsibility. Keep Active set for the group when ready.Save Changes and reopen the selections. Submit one controlled article through the normal review workflow as an eligible author. Confirm the expected reviewer can act and an excluded author/reviewer does not gain that route merely because the group exists.Complete the article’s own review/publication process and verify its intended audience. The group defines review eligibility; it does not grant unrestricted publication permission or guarantee that an article is immediately published. Troubleshooting ProblemWhat to checkA submitted article has no expected review routeCheck Active, the submitter/reviewer filters and the consuming Team/authoring configuration.An inactive group remains listedThe record is retained; inactivity stops it applying to normal review routing.An unexpected person receives review workReview the actual filter matches and the person’s Team/Agent/asset context.Review completion did not publish the intended versionCheck the article’s own workflow, publication action, scheduling and audience.I cannot maintain review groupsCheck Administer article review groups. Related configuration Knowledge Base → Organize knowledge-base topics and accessKnowledge Base → Configure article templates and AI authoring guidanceKnowledge Base → Manage knowledge-base tags and audiencesKnowledge Base → Configure shared article styles and calloutsPractice KCS: turn support work into trusted, reusable knowledgeCreate, review, schedule, and publish a knowledge article Was this article helpful? Yes No Thank you for your feedback.