Personal tokens, service tokens and sign-in
Every agent connection acts for one person and never has more permissions than that person.
Three ways an agent is identified
| Kind | For | Acts as |
|---|---|---|
| Sign-in (OAuth) | Claude Code via /mcp, claude.ai, other OAuth clients | The person who signed in |
| Personal token | One machine or tool, with an expiry | Its owner |
| Service token | CI: the GitHub check and test results | The person with the Integrations permission who created it |
Rules
- A connection belongs to one project.
- Read is always on; propose must be granted.
- Tokens are shown once and stored only as a hash.
- Lowering someone to viewer removes their connection's propose permission; removing them from the tenant ends it.