Hugging Face enterprise security and access controls are the features that the Hub reserves for paid organization plans. They matter to licence management because the plan decides which identity model, audit trail and provisioning route an organization can use, and because some of them change how members are counted. The Team and Enterprise plans documentation lists the features across four tiers: Free, Team, Enterprise and Enterprise Plus.[1]
Editions
| Feature | Free | Team | Enterprise | Enterprise Plus |
|---|---|---|---|---|
| Basic SSO to the private organization | No | Yes | Yes | Managed SSO |
| SSO to the public Hub | No | No | No | Yes |
| Enforce 2FA | No | Yes | Yes | Yes |
| Audit logs | No | Yes | Yes | Yes |
| Resource groups | No | Yes | Yes | Yes |
| Feature access per resource group | No | No | Yes | Yes |
| Tokens administration | No | Yes | Yes | Yes |
| Token revocation | No | No | Yes | Yes |
| Service accounts | No | No | Yes | Yes |
| SCIM provisioning | No | No | Invitation-based | Full lifecycle |
| Network access controls and content access policy | No | No | No | Yes |
| Support | Forum | Best effort | Email with SLA | Slack |
The table is drawn from the plan comparison.[1] The same page shows data residency, default-private repositories, hiding the member list and Gating Group Collections as Team features, and OAuth Token Exchange as an Enterprise feature.[1] Enterprise Plus alone lists disabling personal public repositories for users, disabling joining other organizations, disabling the PRO subscription and Hub-wide controls.[1] See Managed SSO is an Enterprise Plus feature that replaces the Hugging Face login, SCIM is invitation-based on Enterprise and full lifecycle on Enterprise Plus, Token policies are a Team and Enterprise feature and Network security and content access policy are Enterprise Plus only.
Basic and Managed SSO
Hugging Face offers two SSO models. Basic SSO is part of Team and Enterprise, is self-service from the organization settings, does not replace the Hugging Face login, and leaves users with their personal accounts and multi-organization membership. Managed SSO is part of Enterprise Plus, needs setup with the Hugging Face team, replaces the Hugging Face login entirely so that the identity provider is the only way to sign in, and puts accounts under organization ownership.[2] Managed users cannot create content in a personal namespace, cannot join other organizations and must use a separate unmanaged account for personal projects.[3] Both models support SAML 2.0 and OIDC, role mapping and resource group mapping.[2]
SCIM
SCIM is part of Enterprise and Enterprise Plus. With Basic SSO it automates the invitation of existing Hugging Face users: the user must already have an account, receives an invitation email and must accept it, SCIM cannot modify the profile, and deprovisioning deactivates the invitation and revokes access. With Managed SSO it creates accounts, adds users immediately, can update names, emails and usernames, and deactivates the account on deprovisioning.[4] SCIM also supports group provisioning, and groups pushed from the identity provider can be linked to resource groups.[4] For a licence manager the difference is who owns the account: under Managed SSO the organization owns it, and under Basic SSO it remains the individual’s personal account.
Metrics
The plan features are not separate metrics. They determine how the Seat is reached and controlled. The relevant counting rules are:
- Seats follow organization members at renewal.[15]
- Service accounts “are not counted as billable members of your organization”, so creating them does not consume a paid seat.[11]
- Rate limits apply to each member individually, and Enterprise Plus organizations with “Higher Hub Rate Limits” enabled get 100,000, 500,000 and 10,000 requests per 5-minute window for API, resolver and page requests.[14]
Counting / floors
Resource groups and spend
Resource groups let administrators group repositories and give members one of four roles (read, contributor, write, admin) per group. A private repository in a group is visible only to its members, and each repository can belong to only one group.[5] Administrators can restrict features such as Blog, Collections, Jobs, Inference Endpoints and Inference Providers to members of specific groups, attribute costs to a group and cap monthly compute spend per group in total or per product.[6] Granular per-group feature access is listed from Enterprise.[1] See Resource groups can attribute and cap compute spend and Service accounts do not consume a paid seat.
Audit logs
Audit logs, part of Team and Enterprise, let administrators review actions by members, including organization membership, repository settings and billing changes. Each entry includes who acted, the action type, a description, location and anonymized IP address, and the time, and the log can be downloaded as JSON or exported by API.[7] For an asset manager this is the nearest equivalent to a usage record, and it records billing and payment events, but it is not a licence compliance report.
Token policies
Team and Enterprise administrators can enforce one of three token policies: allow user access tokens (the default), allow only fine-grained tokens, or require administrator approval, under which unscoped tokens are unauthorized and fine-grained tokens need approval unless created by an administrator.[8] Token revocation by API is listed from Enterprise.[1]
Network security
Network security is part of Enterprise Plus. Administrators list the organization’s outbound IP ranges in CIDR format, and enforcing login for users in those ranges needs a manual verification carried out jointly with Hugging Face solution engineers. An organization can restrict access to its resources to those ranges only, including for access tokens, and can define a content access policy that blocks repository types, organizations or specific repositories.[9] Service account tokens can be exempted for automation that runs outside the corporate network.[9]
Storage regions and advanced security
Team and Enterprise organizations can choose where new repositories are stored. The documented regions are the US and the EU, with Asia-Pacific and GCC regions described as coming soon, and for users without those plans repositories are always stored in the US.[10] Some compute options such as ZeroGPU may not be available in all regions.[10] Advanced security adds mandatory 2FA, admin approval for new users with a verified domain, a hidden members list and default repository visibility settings (public by default, private by default or private only).[12] See Repositories are stored in the US unless a Team or Enterprise region is chosen.
Gating Group Collections
Gating Group Collections, a Team and Enterprise feature, let an organization grant or reject access to all models and datasets in a collection with a single access request.[13] The licence aspects of gating are described in model and dataset licences and gating.
Virtualization & partitioning
Not applicable. The controls are organization settings and do not depend on processors or virtual machines.
Cloud / BYOL
Not applicable to these features. Organization billing through an AWS or Google Cloud marketplace is described in Hugging Face Hub plans, seats and storage.
Programs
The plan comparison lists pilot availability for Enterprise Plus only, and the page publishes no duration or price.[1] See Enterprise Plus pilot. Enterprise Plus is also the plan with “customer paper” contracts and legal review, and Enterprise uses a Hugging Face template contract.[1]
Out of scope
This article does not explain how to configure an identity provider, does not cover the security certifications or the technical architecture of the Hub, and does not cover Academia Hub governance. Deciding whether Managed SSO’s restrictions on personal content suit an organization is practitioner judgement and is not a Hugging Face statement.