<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> A strategic 1150 Premium seats [Customer](https://gitlab.my.salesforce.com/0016100000sPtnzAAC) needs to have means to block some roles in their company to download the entire repository code. This, in other words, means avoiding them exporting projects/groups, downloading repositories, and cloning repositories through SSH and HTTPS. This is a request from their security team. The roles that should have access to code just through the UI are: - Implementation managers; - Product Managers; - Tech support; Some potential related issues and epics are: - Ability to disable the Download a Copy of the repo button: https://gitlab.com/gitlab-org/gitlab/-/issues/17032 - Customizable Roles and Permissions: https://gitlab.com/groups/gitlab-org/-/epics/4035#note_1094159098 cc: @etugarinova <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->