OAuth Scopes Reference
Search documented OAuth 2.0 scope names across GitHub, Google, Microsoft, Meta, X, Slack and Stripe. Compare saved requested and granted scope lists by exact spelling on your device.
Compare Requested and Granted OAuth Scopes
Selected provider documentation checked . Browsing and comparison run on your device.
81 matching scopes
read:userGitHub · Profile
Read profile data.
user:emailGitHub · Profile
Read the account's email addresses.
user:followGitHub · Profile
Follow and unfollow other users.
userGitHub · Profile
Read and update the user's profile. Includes user:email and user:follow.
public_repoGitHub · Repositories
Read and change public repositories and related resources.
repoGitHub · Repositories
Read and change public and private repositories. It also covers some organization resources.
repo:statusGitHub · Repositories
Read and change commit statuses without code access.
repo_deploymentGitHub · Repositories
Read and change deployment statuses without code access.
read:repo_hookGitHub · Repositories
Read and ping repository webhooks.
read:orgGitHub · Organizations and account
Read organization and team membership and organization projects.
write:orgGitHub · Organizations and account
Read and change organization membership and projects.
admin:orgGitHub · Organizations and account
Manage organizations, teams, projects and memberships.
These scopes are for OAuth Apps. GitHub Apps use a separate permissions model. GitHub can omit a narrower scope from a saved grant when a listed scope already includes it. Provider documentation
OAuth Scopes Reference: how to use it
- Choose Browse scopes, select a provider or leave All providers selected, then search for a name or action such as calendar or user:email.
- Copy the exact scope string and use Source to check its documented effect for the intended endpoint and grant type.
- Choose Compare lists, select the provider and delimiter, and paste the decoded requested and granted scope names. Review the three result groups or download the JSON comparison.
Limits and notes
The dated reference lists selected scopes for seven providers. Each list accepts up to 150 entries and 12,000 characters. The comparison preserves case, counts duplicates once and reports literal membership. Provider rules determine effective grants and endpoint access.
How your privacy works →OAuth Scopes Reference: common questions
Why can GitHub omit user:email from the granted list?
The GitHub OAuth Apps user scope includes user:email. GitHub can normalize a saved grant by dropping scopes already covered by another listed scope. Check GitHub’s documented normalization before interpreting a requested-only name.
Do similar OAuth scope names mean the same thing across providers?
Each provider documents its own resources and grant rules. An identical name can have provider-specific meaning. Choose the correct provider and check the exact endpoint.
What does Outside this snapshot mean?
The exact string is absent from the selected provider’s saved reference. Check its case, product, endpoint and current provider documentation.
Can a Stripe Connect platform use read_only?
Stripe limits Connect OAuth read_only to registered extensions. It requires read_write for Connect platforms and directs new read-only integrations to Stripe Apps.