← All permissions
Repository permission·deployments:read
Deployments: Read
Tier 3 · Low
Why Tier 3
Reads deployments and their statuses.
Data plane permissions start at Tier 2. This one is lowered for the reason above.
- Target
- Repository
- Plane
- DataWorkflows: Workflow files and runs, variables, deployments, environments and Pages.
- Granted by
- Fine-grained PAT, GitHub App, GITHUB_TOKEN
- Available on
- Every setup
- In a workflow
permissions: deployments: read
What it unlocks
4 REST endpoints need this permission. A few of them:
- GET /repos/{owner}/{repo}/deployments
- GET /repos/{owner}/{repo}/deployments/{deployment_id}
- GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses
- GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses/{status_id}
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.