Skip to content

Create "inherit down" toggle for group project templates

Problem to solve

Currently, instance project templates are implicitly granted access to anyone who can see the projects. Group project templates however, require explicit permissions be granted/maintained to each subgroup beneath a parent group in order to see use templates. Why are these two treated differently? Is this how it is intended to work? Without this functionality, this makes group project templates very limiting. Am I thinking about this in the wrong way?

Example (assume all groups/projects are 'internal`)
GitLab\
---InstanceProjectTemplates\ (members: admins)
---|---template_1
---|---template_2
---ParentGroup\ (members: A, B)
---|---ParentGroupProjectTemplates\
---|---|---template_3
---|---|---template_4
---|---SubGroup_1 (members: A, B, C)
---|---SubGroup_2 (members: A, B, D)

With the above diagram, members C & D would only have access to template 1 & 2 because instance templates "inherit down", group templates don't.

Proposal

Implement a toggle on group project templates settings to allow "inherit down" on templates to be enabled (disable by default to match current functionality)

Edited by Jason Drumright