Is your feature request related to a problem? Please describe.
Currently all requests for access are channeled into a single group with a large number of admins. Different admins are responsible for different sets of resources, and have to spend time reviewing each request to see if it relates to resources they are responsible for. This leads to a lot of lost time for every admin in the group and creates potential for mistakes in approving resources they are not responsible for
Describe the solution you'd like
Create the ability to define a tag on resources such as "approver=groupA, approver=groupB" and then create slack channels for each approver group - this would limit the noise for each approver group significantly and ensure confidence they are approving only requests relevant to them
Describe alternatives you've considered
The only other possibility I can see is setting the approver based on the requester - so adding a tag to all roles "approver=groupA, approver=groupB" so that the approval flow is based on the requester rather than the resource. This may not work as the manager of a group/role may not be the ultimate owner of the infra for which access is being requested
Is your feature request related to a problem? Please describe. Currently all requests for access are channeled into a single group with a large number of admins. Different admins are responsible for different sets of resources, and have to spend time reviewing each request to see if it relates to resources they are responsible for. This leads to a lot of lost time for every admin in the group and creates potential for mistakes in approving resources they are not responsible for
Describe the solution you'd like Create the ability to define a tag on resources such as "approver=groupA, approver=groupB" and then create slack channels for each approver group - this would limit the noise for each approver group significantly and ensure confidence they are approving only requests relevant to them
Describe alternatives you've considered The only other possibility I can see is setting the approver based on the requester - so adding a tag to all roles "approver=groupA, approver=groupB" so that the approval flow is based on the requester rather than the resource. This may not work as the manager of a group/role may not be the ultimate owner of the infra for which access is being requested
Additional context N/A
IMPORTANT: Remember to select a label and project