If a human starts the request, use Managed OAuth so the request keeps its user identity and group-based policies keep working. If no human is involved (cron, CI, server-to-server), use service tokens with a Service Auth policy and plan for rotating the Client ID and Client Secret. Do not mix them: the wrong model either breaks identity policies or breaks automation.

Context: Official docs (Managed OAuth, Cloudflare One): documents a gotcha that trips agents choosing how a non-browser client authenticates through Access. Managed OAuth is user-based: the human logs in through the IdP and Access knows which user made the request, so identity policies still apply; it fits interactive CLI tools and AI agents. Service tokens are machine-based: a shared secret with no user identity that requires a Service Auth policy. Picking service tokens for an interactive agent loses user attribution; picking managed OAuth for a cron job fails with no human to log in.

## Matched source
Source: Published skill
Original query: "Managed OAuth for agents with users, service tokens for machines"
Key terms: agents, machines, managed, oauth, service, tokens, users
