Skip to content

docs: document assigning collections to resource groups#2618

Open
Kakulukian wants to merge 1 commit into
mainfrom
auto-docs/moon-landing-pr-18534
Open

docs: document assigning collections to resource groups#2618
Kakulukian wants to merge 1 commit into
mainfrom
auto-docs/moon-landing-pr-18534

Conversation

@Kakulukian

@Kakulukian Kakulukian commented Jul 2, 2026

Copy link
Copy Markdown
Member

Collections can now be assigned to a Resource Group (Team & Enterprise), following the same access-control and visibility rules as repositories.


Note

Low Risk
Documentation-only updates with no application, API, or security logic changes.

Overview
Documents Team & Enterprise support for tying organization collections to Resource Groups, mirroring repository access control.

collections.md adds a section on choosing a Resource Group at creation, moving collections via the collection menu, and limiting visibility of private collections to group members, with a link to security-resource-groups.

security-resource-groups.md states that collections follow the same one-group-per-resource rules as repos and that private collections in a group use the same visibility rules as private repos in that group.

Reviewed by Cursor Bugbot for commit e2e0646. Bugbot is set up for automated code reviews on this repo. Configure here.

Collections can now be assigned to a Resource Group (Team & Enterprise),
following the same access-control and visibility rules as repositories.
@HuggingFaceDocBuilderDev

Copy link
Copy Markdown

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants