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/enterprise-hub-gating-group-collections.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ To enable Gating Group in a collection:
11
11
- the collection owner must be an organization
12
12
- the organization must be subscribed to the Enterprise Hub
13
13
- all models and datasets in the collection must be owned by the same organization as the collection
14
-
- each model or dataset in the collection may only belong to one Gating Group Collection, but they may be present on non-gating collections.
14
+
- each model or dataset in the collection may only belong to one Gating Group Collection (but they can still be included in non-gating i.e. _regular_collections).
15
15
16
16
<Tip>
17
17
Gating only applies to models and datasets; any other resource part of the collection (such as a Space or a Paper) won't be affected.
@@ -146,7 +146,7 @@ There is currently no way to customize the gate parameters and requested informa
146
146
147
147
## Access gated repos in a Gating Group Collection as a user
148
148
149
-
A Gated Group Collection shows a specific icon before its name:
149
+
A Gated Group Collection shows a specific icon next to its name:
0 commit comments