Process Flow - Why advanced IAM matters
User requests access
Check basic IAM roles
Access granted
Access granted
This flow shows how access is first checked with basic roles, then advanced IAM policies are evaluated for finer control.
1. User requests access to resource 2. System checks basic IAM roles 3. If no basic role, system checks advanced IAM policies 4. Access granted or denied based on checks
| Step | Action | Check | Result | Next Step |
|---|---|---|---|---|
| 1 | User requests access | N/A | Request received | Check basic IAM roles |
| 2 | Check basic IAM roles | Does user have basic role? | No | Check advanced IAM policies |
| 3 | Check advanced IAM policies | Does user meet advanced conditions? | Yes | Access granted |
| 4 | Access granted | N/A | User allowed access | End |
| Variable | Start | After Step 2 | After Step 3 | Final |
|---|---|---|---|---|
| UserAccessRequest | None | Received | Evaluated | Granted |
| BasicRoleCheck | Not checked | No role found | N/A | N/A |
| AdvancedIAMCheck | Not checked | Not checked | Conditions met | Access allowed |
GCP IAM controls access by checking basic roles first. If basic roles don't grant access, advanced IAM policies apply. Advanced IAM allows fine-grained permission control. Access is granted only if checks pass. This layered check improves security and flexibility.