Skip to content

Clarify when the `minimal access` role can consume a seat

Chantal Lawrence requested to merge Clarify-minimalAccessRole into master

What does this MR do and why?

The current definition of the Minimal access role in our docs is misleading and can easily be misunderstood if the reader has limited or no prior knowledge about how we calculate seat usage.

Currently the page states:

Users with the Minimal Access role do not:

  • Count as licensed seats on self-managed Ultimate subscriptions or any GitLab.com subscriptions.
  • Automatically have access to projects and subgroups in that root group.

I have changed the order (priority?) of these two point and made a slight change to provide a clearer definition:

Users with the Minimal Access role do not:

  • Automatically have access to projects and subgroups in that top level group.
  • Count as licensed seats on self-managed Ultimate subscriptions or any GitLab.com subscriptions, provided the user has no other role anywhere in the instance or in the GitLab SaaS namespace.

Related Ticket: https://gitlab.zendesk.com/agent/tickets/477282

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Chantal Lawrence

Merge request reports