# Identity propagation

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Carrying who is asking, and who is acting, through each hop between a user, an agent and the services it calls. Propagation lets a downstream service apply the right authority and lets the logs name both parties. Where it is missing, calls arrive as the agent alone.

## An example, sourced

Google documents a three-identity framework for agents: the user identity establishes caller context at ingress, the agent identity authenticates the workload within the runtime boundary, and a delegated identity combines both authorities when the agent accesses downstream services on behalf of the user. Google's architecture page describes how each identity layer propagates across the trust boundaries on the way. Google places the user, the agent and the delegated identity in separate trust boundaries.

## Why it matters here

Propagation decides whether a downstream log line names the person, the agent or only a shared role. If a platform does not propagate, the review should say so and rely on controls elsewhere. Treat a missing link in the chain as a finding and not as a detail.

## Related pages

- [Model invocation logging: meaning and an example](/glossary/model-invocation-logging/)
- [CloudTrail data events: meaning and an example](/glossary/cloudtrail-data-events/)
- [Cloud Audit Logs: meaning and an example](/glossary/cloud-audit-logs/)
- [All of them](/glossary/)

## Sources

- https://docs.cloud.google.com/gemini-enterprise-agent-platform/govern/identity-delegation-architecture (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/identity-propagation/
