However given a Team has a number of Environments (e.g. Dev, Staging, Production) along with dynamic Preview Environments it can be a challenge keeping all the Role and RoleBinding resources from Kubernetes RBAC in sync with all the various namespaces and members of your team.
So Jenkins X creates a new Custom Resource called EnvironmentRoleBinding which allows you to associate a Role labelled with jenkins.io/kind=EnvironmentRole with as many Users or ServiceAccounts as you like and a selection of Environments. Then as Environments are created or the Role or EnvironmentRoleBinding in the Dev environment is modified, the role controller ensures that the EnvironmentRole is replicated to all the environment namespaces as a Role and RoleBinding per namespace
The role controller is included by default inside Jenkins X or you can run it by hand via jx controller role
Jenkins X ships with a bunch of default Role objects you can use in the jenkins-x-platform template. You can disable any of these roles via configuration and and create your own if you wish.