Skip to content

Commit 779c180

Browse files
VioletteLepercqCharlie-BoyerPierrci
authored
Update enterprise-hub-network-security.md (#2124)
* Update enterprise-hub-network-security.md * Update docs/hub/enterprise-hub-network-security.md Co-authored-by: Charlie <57417805+Charlie-Boyer@users.noreply.github.com> * Update docs/hub/enterprise-hub-network-security.md Co-authored-by: Pierric Cistac <Pierrci@users.noreply.github.com> --------- Co-authored-by: Charlie <57417805+Charlie-Boyer@users.noreply.github.com> Co-authored-by: Pierric Cistac <Pierrci@users.noreply.github.com>
1 parent 434609e commit 779c180

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/hub/enterprise-hub-network-security.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,12 @@ You can set multiple ranges, one per line.
1515
<img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/enterprise/dark-network-sec-ip-ranges.png" alt="Screenshot of the Organization IP Ranges field."/>
1616
</div>
1717

18+
Once organization admins populate the “Organization IP Ranges” in the Network Security settings, a manual verification—carried out jointly by Hugging Face Solution Engineers and the organization’s admins—is required for the "Require login for users in your IP ranges" setting to become available.
19+
20+
After the “Organization IP Ranges” have been manually verified, and the organization admins have enabled both “Restrict organization access to your IP ranges only” and “Require login for users in your IP ranges”, the following flow applies:
21+
- When a user arrives on the platform, their IP address is checked.
22+
- If the IP falls within the organization’s defined ranges, the user must authenticate (via the organization’s SSO if enabled).
23+
- Once authenticated, the Content Access Policy determines which resources the user can access.
1824

1925
## Higher Hub Rate Limits
2026

0 commit comments

Comments
 (0)