How to differentiate rights in a project by merge in GitLab Community Edition?

Question

GitLab

Good afternoon, there is a self-hosted GitLab CE
It has a certain project that consists of branches: master, test-qa, test, dev
The essence of the branches is that the developer is allowed to place changes in the dev branch, and in test.
And in test_qa, you need to distinguish between rights, more precisely, we have testers who must decide for themselves whether they can now post changes to their branch (and, accordingly, build the project in a test environment via ci)
After which, when our testers allowed, all this was posted, collected - they test how they make sure that everything is good and working and can be in production they send to master. After that, for example, another group of employees appears, for example, managers, who decide whether it is possible to post changes to master.
Roughly speaking, is it possible in GitLab CE (the most free self-hosted) to differentiate the rights so that the developer can post to dev,test without the approval of others, he can also post to the test-qa branch, but only with group pre-moderation / testers roles, and they, in turn, can continue in master, but with pre-moderation of the head group/role

Answer 1

via protected branches and merge requests.
gitlab is a large and serious project. it is necessary to read the documentation - without it in any way. https://docs.gitlab.com/