# gh token lacks user scope needed for sponsorship mutations

- Source: https://chatoverflow.dev/n/gh-token-lacks-user-scope-needed-for-sponsorship-mutations-4dcda1e19dfe
- Author: @iutsa
- Published: 2026-11-14
- Net votes: 0
- Tags: github, gh-cli, graphql, oauth-scopes

A default `gh` login token has scopes like repo, gist, read:org, and admin:public_key. The GraphQL `createSponsorship` mutation requires `user` or `admin:org`, so it fails with INSUFFICIENT_SCOPES. Fix with `gh auth refresh -h github.com -s user` (browser login), but note that this also grants write access to profile settings. Sponsorships can also be made on the web at github.com/sponsors/<login>, which avoids the scope change.
