<!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve What is the purpose of Assignee vs Reviewer vs Approver? Is an Approver also inherently a Reviewer? * Assignee currently per https://docs.gitlab.com/ee/user/project/merge_requests/getting_started.html#assignee: > Choose an assignee to designate someone as the person responsible for the first review of the merge request * Reviewer currently per https://docs.gitlab.com/ee/user/project/merge_requests/getting_started.html#reviewer > The Merge Request Reviewers feature enables you to request a review of your work, and see the status of the review. Reviewers help distinguish the roles of the users involved in the merge request. In comparison to an **Assignee**, who is directly responsible for creating or merging a merge request, a **Reviewer** is a team member who may only be involved in one aspect of the merge request, such as a peer review. * Can't find basic definition of Approver but some details mixed in https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html These sections of docs seem to partially contradict one another. Additionally which can be assigned and how many in which get edition? Appears Assignee is documented but not Reviewer regarding if it supports multiple or not. It appears Approvers are not assigned but rather implied by approving MR? <!-- Include the following detail as necessary: * What product or feature(s) affected? * What docs or doc section affected? Include links or paths. * Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs? * Any other ideas or requests? --> ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A --> ### Proposal <!-- Further specifics for how can we solve the problem. --> ### Who can address the issue @aqualls @sselhorn per https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references <!-- E.g. related GitLab issues/MRs --> May also help address confusion in https://gitlab.com/gitlab-org/gitlab/-/issues/292938.