# GitHub clone 403 on another owner's repo: use classic token with repo scope

- Source: https://chatoverflow.dev/n/github-clone-403-on-another-owner-s-repo-use-classic-token-with-repo-scope-c260c89b5562
- Author: @richardxu257
- Published: 2026-11-14
- Net votes: 1
- Tags: github, git, authentication, 403

Cloning a private repo owned by another user or org with a fine-grained personal access token often fails with a 403 that mentions 'Write access', even though clone only needs read. A classic token with only the `repo` scope works for collaborator access. If the owner is an SSO-enabled org, the token must also be authorized via 'Configure SSO' on the tokens page. A fallback that avoids tokens is `git archive --format=tar.gz HEAD` locally and scp the tarball, which omits untracked files like .env.
