Skip to content

Document per-resource-group feature access for organizations - #2697

Merged
Pierrci merged 7 commits into
mainfrom
auto-docs/moon-landing-pr-18893
Aug 12, 2026
Merged

Document per-resource-group feature access for organizations#2697
Pierrci merged 7 commits into
mainfrom
auto-docs/moon-landing-pr-18893

Conversation

@Kakulukian

@Kakulukian Kakulukian commented Aug 11, 2026

Copy link
Copy Markdown
Member

Org admins on Enterprise plans and above can now restrict Blog, Collections, Jobs, Inference Endpoints and Inference Providers to org admins only or to the members of specific resource groups, from the new "Access settings" tab of the Resource Groups settings page.

  • Add a "Feature access" section to the Resource Groups guide
  • Note the new tab layout, including where the "who can create resource groups" setting now lives
  • Mention feature access in the Enterprise resource groups overview and in the plan comparison table

Note

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

Overview
Documents granular feature access for Enterprise orgs: admins can limit Blog, Collections, Jobs, Inference Endpoints, and Inference Providers to everyone, org admins only, or members of selected resource groups.

The Resource Groups guide adds a Granular feature access section (with UI screenshots), clarifies that settings live on the new Access settings tab alongside Resource Groups, and updates where the “who can create resource groups” control is described. The enterprise resource groups overview and enterprise.md plan comparison table now call out feature access per resource group as Enterprise / Enterprise Plus only.

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

Org admins on Enterprise plans and above can now restrict Blog,
Collections, Jobs, Inference Endpoints and Inference Providers to org
admins only or to the members of specific resource groups, from the new
"Access settings" tab of the Resource Groups settings page.

- Add a "Feature access" section to the Resource Groups guide
- Note the new tab layout, including where the "who can create resource
  groups" setting now lives
- Mention feature access in the Enterprise resource groups overview and
  in the plan comparison table

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

HuggingFaceDocBuilderDev commented Aug 11, 2026

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.

@Kakulukian
Kakulukian marked this pull request as ready for review August 11, 2026 12:00
@Kakulukian
Kakulukian requested a review from Pierrci August 11, 2026 12:00
Comment thread docs/hub/security-resource-groups.md Outdated
Co-authored-by: Pierric Cistac <Pierrci@users.noreply.github.com>
Comment thread docs/hub/security-resource-groups.md Outdated
@Pierrci

Pierrci commented Aug 12, 2026

Copy link
Copy Markdown
Member

@moonbot update the links following my last commit moonbot is not here 🥲

Pierrci and others added 2 commits August 12, 2026 12:46
Commit 62b98f5 renamed the `## Feature access` section to
`## Granular feature access`, which changed the anchor from
`#feature-access` to `#granular-feature-access`. Update the
enterprise feature-comparison table link so it still resolves.

Co-Authored-By: Claude <noreply@anthropic.com>
Previous anchor fix left row 1 misaligned with the rest of the column
after the longer `#granular-feature-access` target. Re-pad the first
column so all rows share one width.

Co-Authored-By: Claude <noreply@anthropic.com>
@Pierrci
Pierrci merged commit 688fba0 into main Aug 12, 2026
3 checks passed
@Pierrci
Pierrci deleted the auto-docs/moon-landing-pr-18893 branch August 12, 2026 16:50
Pierrci added a commit that referenced this pull request Aug 12, 2026
* Document per-resource-group feature access for organizations

Org admins on Enterprise plans and above can now restrict Blog,
Collections, Jobs, Inference Endpoints and Inference Providers to org
admins only or to the members of specific resource groups, from the new
"Access settings" tab of the Resource Groups settings page.

- Add a "Feature access" section to the Resource Groups guide
- Note the new tab layout, including where the "who can create resource
  groups" setting now lives
- Mention feature access in the Enterprise resource groups overview and
  in the plan comparison table

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

* chore: add image, rewrite a bit

* alignment

* Link restrictable-feature docs to the Feature access section

Add cross-links to the new Feature access section of security-resource-groups.md
from the docs for features it can restrict:

- enterprise-blog-articles: the existing note claimed Blog "cannot be scoped
  using Resource Groups". That is now stale — Feature access (Enterprise+) lets
  org admins restrict who can write/publish org blog articles. Reword the note
  to distinguish per-repo Resource Group scoping (still N/A to blog) from
  Feature access gating, and link through.
- collections: add a note distinguishing assigning a collection to a Resource
  Group (per-collection visibility) from Feature access (who can create/edit
  org Collections at all).
- jobs-pricing: note that Feature access can restrict who runs/views Jobs
  billed to the organization.

Stacked on #2697.

Co-Authored-By: Claude <noreply@anthropic.com>

* Apply suggestions from code review

Co-authored-by: Pierric Cistac <Pierrci@users.noreply.github.com>

* Apply suggestion from @Pierrci

* Apply suggestions from code review

Co-authored-by: Pierric Cistac <Pierrci@users.noreply.github.com>

---------

Co-authored-by: huggingface-doc-bot <doc-bot@huggingface.co>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Sylvestre <sylvestre@huggingface.co>
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.

3 participants