docs: publisher gating setting (#2504)

* Document Publisher Gating for Enterprise Plus organizations

Adds a new page describing the Publisher Gating org setting, which lets
Enterprise Plus admins automatically reject gated repo access requests
originating from selected countries. Cross-links from the gated models
and datasets pages and adds rows to the Enterprise plan comparison.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Polish Publisher Gating docs style

Co-authored-by: Cursor <cursoragent@cursor.com>

* Revert previous doc & mention it in gating group collections

* Rename new gating group collections section

Co-authored-by: Julien Chaumond <julien@huggingface.co>

---------

Co-authored-by: huggingface-doc-bot <doc-bot@huggingface.co>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Julien Chaumond <julien@huggingface.co>

Author: 5 people

docs/hub/enterprise-gating-group-collections.md

@@ -141,6 +141,10 @@ Organizations can customize the gating parameters as well as the user informatio
 > [!WARNING]
 > There is currently no way to customize the gate parameters and requested information in a centralized way. If you want to collect the same data no matter which collection's repository a user requests access throughout, you need to add the same gate parameters in the metadata of all the models and datasets of the collection, and keep it synced.
 
+## Advanced settings
+
+Enterprise Plus organizations can define **blocked countries** to automatically reject access requests across their gated models and datasets. This setting is available in the **Publisher Analytics** settings, under the **Advanced Gating** tab.
+
 ## Access gated repos in a Gating Group Collection as a user
 
 A Gated Group Collection shows a specific icon next to its name: