<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=31332) </details> <!--IssueSummary end--> ### Problem to solve <!-- What problem do we solve? --> ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> This feature is intended to be used in multiple team triggers pipelines. In my case i want developers upstream project to trigger a pipeline build on a SRE repository without having right to push/merge on master. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> Currently user must have right to push or merge to make a trigger downstream pipeline to be launched. Having a right to launch pipeline permits external users to the repository to launch deployments without having right to modify the deployment code. It's useful in a dev/sre environment where dev(ops) is focusing on creating a package and SRE are focusing on deployment across projects. This right can be useful also on modular applications with many developers permitting library owners to trigger rebuild on downstream artifacts to ensure their lib works with the downstream projects of other teams. :warning: Currently the trigger is stuck in pending state when user doesn't have permission instead of failing due to permissions, feedback from UI is not good ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> I propose to add a new right "Pipeline" to launch pipeline in the protected branch view. This will permit to delegate end users pipeline launch without modifying code. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> Only owner can change permissions. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references