## Description Today, we limit no more than 5 pipeline execution policies can be created within a single level of the GitLab structure. For instance, only 5 PEPs at the top level group, only 5 per sub-group. We also limit no more than 5 policies targeting a single project. For many customers (such as self-managed customers), they leverage multiple top level groups. For GitLab.com and Dedicated they may also only have one top-level group. When moving from compliance pipelines, limits related to compliance frameworks that can be created with pipelines exceed that of the limits defined for PEP at the same level. This Epic will explore any suitable improvements to our limits to support customer use cases as well as ensuring performance/scalability. ## Proposal 1. Provide a configuration option for Administrators to manage the limit of pipeline execution policies per security policy project. 2. Set a default limit of 5 pipeline execution policies, with an option to increase the limit to 20. 3. The limit of 5 pipeline execution policies per project would remain. 4. Self-managed customers would be able to modify this limit. Dedicated limits could be managed by GitLab administrators. GitLab.com would be continue to be limited to 5 and limits again managed by GitLab administrators.