A policy binding connects a principal to a role at a resource scope. Read the principal type as well as its identifier. A user, a group and a service account are different subjects, even when their labels refer to the same business service.
These tasks save approved project bindings and distinguish inspection from data access. The checker examines the resulting principal, role and target project. It doesn't match command text or evaluate a real authorization request. Other applicable controls may affect production access, so keep that limitation in your handoff. A broad role isn't a shortcut around finding the action and scope that the owner approved.
Bind the intended principal and narrow role on the intended project.