You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hub/collections.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Collections have many use cases:
11
11
- Showcase and share a complete project with its paper(s), dataset(s), model(s) and Space(s).
12
12
- Bookmark things you find on the Hub in categories.
13
13
- Have a dedicated page of curated things to share with others.
14
-
- Gate a group of models/datasets (Enterprise only)
14
+
- Gate a group of models/datasets (Enterprise Hub)
15
15
16
16
This is just a list of possible uses, but remember that collections are just a way of grouping things, so use them in the way that best fits your use case.
17
17
@@ -55,13 +55,13 @@ Use the **history feature** to keep track of who has edited the collection.
55
55
56
56
Set your collection to **private** if you don't want it to be accessible via its URL (it will not be displayed on your profile/organization page). For organizations, private collections are only available to members of the organization.
57
57
58
-
### Gating Group Collection (Enterprise only)
58
+
### Gating Group Collection (Enterprise Hub)
59
59
60
60
For [Enterprise Hub](https://huggingface.co/docs/hub/en/enterprise-hub) subscribers, you can gate all the repos in a collection, enabling **a single access requests** for all models and datasets in it.
61
61
62
-
This feature allows you to restrict access to specific collections: users must agree to share their contact information (username and email address) with the organization to access the models and datasets files when enabled.
62
+
This feature allows you to restrict access to specific collections: users must agree to share their contact information (username and email address) with the organization to access the models and datasets in a gating group collection.
63
63
64
-
Please note that this feature is only available to Enterprise subscribers: more information about Gating Group Collection can be found in [our doc](https://huggingface.co/docs/hub/en/enterprise-hub-gating-group-collections).
64
+
Please note that this feature is only available to Enterprise Hub subscribers: more information about Gating Group Collection can be found in [our doc](https://huggingface.co/docs/hub/en/enterprise-hub-gating-group-collections).
Copy file name to clipboardExpand all lines: docs/hub/enterprise-hub-gating-group-collections.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
This feature is part of the <ahref="https://huggingface.co/enterprise">Enterprise Hub</a>.
5
5
</Tip>
6
6
7
-
Gating Group collections allows organizations to configure gate all the repos in a collection, enabling **access requests** for all models or datasets in it.
7
+
Gating Group Collections allow organizations to configure gated access to all the repos in a collection, enabling **a single access request** for all the models and datasets in it.
8
8
9
9
## Manage gating group as an organization admin
10
10
@@ -49,7 +49,7 @@ By default, access to the repos in the collection is automatically granted to th
alt="Hugging Face gating group collection settings with gating with automatic mode selected"
52
+
alt="Hugging Face gating group collection settings with automatic mode selected"
53
53
/>
54
54
</div>
55
55
@@ -68,4 +68,4 @@ If you want to manually approve which users can access repos in your collection,
68
68
/>
69
69
</div>
70
70
71
-
**Notification frequency** lets you configure when to get notified if new users request access. It can be set to once a day or real-time. By default, emails are sent to the first 5 admins of the organization. You can also set a different email address in the **Notifications email** field.
71
+
**Notification frequency** lets you configure when to get notified about new users requesting access. It can be set to once a day or real-time. By default, emails are sent to the first 5 admins of the organization. You can also set a different email address in the **Notifications email** field.
0 commit comments