Skip to content

Max role w/ inheritance and shared group

Brie Carranza requested to merge bcarranza-max-role-shared-group-inherited-docs into master

What does this MR do and why?

This MR starts introducing additional info into the docs about how Max role is considered when a user has access to a project by virtue of both:

  • being an inherited member from the parent group of the project
  • being a member of a group that the project is shared with

This is based on the experience reported by a customer. GitLab team members with access to Zendesk can learn more in the ticket. 🎫

In the docs, we say:

If a user is a:

  • Direct member of a project, the Expiration and Max role fields can be updated directly on the project.
  • Inherited member from a parent group, the Expiration and Max role fields must be updated on the parent group.

That last note about the Max role needing to be updated on the parent group is what helped us in understanding the cause of the confusion.

Docs: Inherited membership

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

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 Brie Carranza

Merge request reports