Token Permissions
An API token authenticates as the user who created it and inherits that user's access. There are no granular per-token scopes today — a token can do what its owner can do.
Current model
| Aspect | Behavior |
|---|---|
| Identity | The token acts as its creating user. |
| Scope | Full access to that user's projects, endpoints, destinations, events, and deliveries. |
| Revocation | Immediate, per token. |
| Expiry | A token may have an expiresAt; after it passes, the token stops working. |
Practical least privilege
Until fine-grained scopes exist, contain risk with these patterns:
- One token per consumer (per pipeline or service) so you can revoke independently.
- Separate projects per environment so a token's reach is naturally bounded.
- Rotate regularly and on personnel changes — see Best practices.
:::info Coming soon Granular, scoped permissions (read-only tokens, per-project or per-resource scopes) are not available yet. This page will be updated when they ship. :::