Ownership verification
How Hugging Face identity and authoritative namespace permissions control who can launch.
5 sections / hugpad handbook
On this page
Repository namespace is the starting point
A repository ID has two parts: namespace/model-name. The namespace identifies the user or organization that publishes it. Merely downloading, liking, contributing to, or mentioning a model does not authorize launching for that namespace.
Who is eligible?
| Your relationship | Launch access |
|---|---|
| Your personal namespace | Eligible when it matches your verified signed-in Hugging Face username. |
| Organization admin | Eligible when Hugging Face authoritatively reports admin access. |
| Organization write member | Eligible when Hugging Face authoritatively reports write access. |
| Read-only member or follower | Not sufficient for launch authorization. |
| Wallet holder or HF-verified profile | Not sufficient on its own; repository access is checked separately. |
Server-side verification
The browser sends your Hugging Face bearer token with protected launch operations. The server calls Hugging Face’s identity endpoint and uses the returned username and organization roles. A browser-supplied ownership flag, display name, or profile badge is not trusted.
The namespace check is applied before uploading media. If Hugging Face cannot verify the token or role, the operation stops rather than proceeding on an assumption.
Why a repository may be missing
The launch selector loads a bounded public-model list for the namespaces your session reports as eligible. It is not a complete private-repository inventory. A repository can be absent because it is private, outside the fetched batch, unavailable upstream, or under an organization whose role is not reported as eligible.
Check the namespace and your current role on Hugging Face, then sign in again if access has changed. Directory visibility does not itself prove launch permission.
Access control is not an IP certificate
Know the scope of the check