# Service account

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

A non-human identity in Google Cloud that a workload runs as. You grant it IAM roles, attach it to a resource such as a Cloud Run service, and the workload calls Google Cloud APIs as that account. Several workloads can share one, which makes the sharing a review question.

## An example, sourced

Google documents user-managed service accounts that you create in a project, and default service accounts that Google Cloud creates for you. For Cloud Run, Google documents that the Compute Engine default service account is the default service identity if you pick none. Google also documents that, depending on organization policy, that account might automatically be granted the Editor role on the project, and recommends replacing Editor with less permissive roles.

## Why it matters here

An agent that inherits a default service account inherits access nobody chose for it. Naming the account in the review, and listing its roles, is how that inheritance is found. The roles on the account, not the account's name, set the real reach.

## Related pages

- [Service agent: meaning and an example](/glossary/service-agent/)
- [Managed identity: meaning and an example](/glossary/managed-identity/)
- [Workload identity: meaning and an example](/glossary/workload-identity/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/run/docs/securing/service-identity (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/service-account/
