Skip to content

Reconsider Disabling Project Sharing with Seat Controls

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

When Seat controls are set to Set user cap or Restricted access (user caps or block seat overages), we disable both sharing with groups outside the hierarchy and inviting groups to projects:

Screenshot_2024-08-26_at_5.40.41_PM

Testing a bit by hand, it seems that if inviting groups from outside the hierarchy is disabled, this also affects inviting groups to projects.

If the first setting is turned off (inviting groups from outside the hierarchy is allowed), then I can invite groups from outside the hierarchy to a project (notice the groups that reside outside Solar System Group, the root of the hierarchy):

Screenshot_2024-08-26_at_5.43.24_PM

However, if the first setting is turned on (inviting groups from outside the hierarchy is forbidden), then I cannot invite groups from outside the hierarchy to a project:

Screenshot_2024-08-26_at_5.44.49_PM

Screenshot_2024-08-26_at_5.44.58_PM

So it seems that we may not necessarily need to enable the second setting when user caps or block seat overages is enabled.

Proposal

Consider if we may want to stop forcibly checking Projects in $GROUP cannot be shared with other groups when we enable user caps (Set user cap) or block seat overages (Restricted access).

It doesn't seem like there is a need to forcibly check Projects in $GROUP cannot be shared with other groups.

Edited by 🤖 GitLab Bot 🤖