Add configuration to include/exclude GitLab provided built-in templates from end users on a self-managed GitLab instance
Problem to solve
Some customers create their own self-managed templates for end-users to choose from and do not want the end-users to confuse the Instance level templates with the built-in templates provided by GitLab. To ease confusion on self-managed instances that use this strategy, we propose to add a configuration to exclude GitLab provided templates from the UI. Only GitLab admins will have the ability to turn this feature on or off.
(I would expect to see this at an organization where customers require a certain type of authentication. For example, assume a customer builds a Spring template that includes a unique authentication method, and they require all projects using Spring to use this Spring template. There would be no reason to even include the GitLab provided Spring template.)
Intended users
GitLab Systems Administrator
User experience goal
The GitLab System Administrator should be able to use the Admin Area Templates UI to configure the GitLab Self-Managed Instance to include or exclude the GitLab provided built-in templates.
Proposal
Add a configuration flag to include/exclude the built-in templates view from the UI. We do NOT need to remove the templates, we just need to hide them which should be solvable from a UI perspective.
Further details
This will be useful for companies/agencies in highly-regulated industries. Many times, highly-regulated industries will have a requirement for an application to be behind some sort of authentication service that is company-provided, often times legacy. In these cases, companies may build on top of GitLab provided templates to create their own for their organization. To avoid confusion, they would want to exclude the built-in templates to their end-users.
Permissions and Security
Only (self-managed) GitLab Administrators would have the ability to turn built-in templates on/off.
Documentation
Assuming this feature is added, we would need to make changes to the following documentation:
Availability & Testing
Unknown
Available Tier
Premium (Self-Managed)
Feature Usage Metrics
Unknown
What does success look like, and how can we measure that?
Unknown
What is the type of buyer?
CISO, CIO, VP of App Dev
Is this a cross-stage feature?
No
What is the competitive advantage or differentiation for this feature?
This will be advantageous for any highly-regulated industry, in particular, the US Public Sector.