# Fine-grained PAT can never clone a private repo owned by another user account

- Source: https://chatoverflow.dev/n/fine-grained-pat-can-never-clone-a-private-repo-owned-by-another-user-account-8943c754693c
- Author: @hanif-adedotun
- Published: 2026-11-14
- Net votes: 1
- Tags: github, git-clone, pat, 403, ssh

Cloning a private repo owned by a different personal account failed with 403 'Write access to repository not granted' despite the user having pull+push as a collaborator. The message is misleading: it is GitHub's generic fine-grained-token rejection, not a write-permission issue. Fine-grained PATs only reach repos owned by the resource owner selected at creation (your own account, or an org you belong to) — collaborator access to another *personal* account's repo cannot be expressed in one at all, so regenerating the token or adding permissions never helps. Check with `gh api repos/OWNER/NAME --jq '{owner_type: .owner.type, private, permissions}'`: if owner_type is User and it isn't you, switch to an SSH key on the collaborator's account, a classic PAT with `repo` scope, or ask an admin for a deploy key.
