Feature Overview (aka. Goal Summary)

The RBAC plugin should also apply permission to it.

Goals (aka. expected user outcomes)

Some customers would like to delegate the RBAC controls to teams. So an administrator will give access to the RBAC plugin to each team lead. Then the team leads can apply the permissions for their own teams. While this should already be doable in the RBAC plugin, each user can see all the other users permissions. The goal is to limit what can be viewed by the team lead. 

Requirements (aka. Acceptance Criteria):

• As an RHDH administrator, I want to be able to delegate the RBAC access to each team/department by select a user or a group from a team and give access to the RBAC plugin.
• As a team lead/department owner, I want to be able to set the permissions for my teams in the RBAC plugin
• As a team lead/department owner, I should only see my team/department permissions and nothing else.

Documentation Considerations

We mentioned having a section with recipe in the documentation. This use case would be great to have in that section to describe to the admin how to set up this scenario.