Skip to main content
Console sidebar → Hugging Face, then Connect. That authorises your own hub account against the platform.
The server injects your token for that push. Nobody shares a team token.

What linking gets you

Scopes

The default authorisation is read-only: openid, profile, email, read-repos, gated-repos. Pushing needs a write scope, which is behind a second switch the deployment controls. Once an administrator sets TUNEPLANE_HF_OAUTH_WRITE_ENABLED=true, re-authorise on the same page to pick up the push scope. Until then, --push-repo is refused rather than failing at upload time.

Check it worked

The Hugging Face page shows your linked account and the scopes you granted. Then submit a job that references a gated repository:
A gated repo you are not approved for is refused at submission, naming the repository. That is the preflight working. Without a link, the same job would queue, start, and die downloading weights. --push-repo is validated as namespace/name, so nothing you type there can become an extra argument. A failed push leaves the local export artifact alone.

For an administrator

The whole integration is off until you configure it:
The sidebar entry is hidden while TUNEPLANE_HF_OAUTH_ENABLED is false, so an unconfigured deployment shows no dead link. TUNEPLANE_HF_OAUTH_BASE_URL points at a mirror on a network that cannot reach huggingface.co.

Next

Pipelines for the export step · Datasets · Air-gapped deployments