Update Resource Groups docs for the redesigned UI

[gary149]

The Resource Groups pages in org settings were redesigned recently, this updates the docs to match.

Changes

• Getting started now describes the resource group page and its four tabs: Overview (summary chips and resource/user previews), Resources, Users, and Settings.
• Auto-join and Spend limits instructions now point at their new home in the group Settings tab, and the auto-join section gained a screenshot.
• All screenshots retaken for the new UI, in light and dark mode at 3x, using a demo org (no real data). The images are already uploaded to the documentation-images dataset under their existing names, so this PR only touches the markdown.
• Accuracy fixes, verified against the actual behavior:
  • "Read+" creation setting excludes members with the no_access org role, the previous wording said any org member.
  • Granular feature access is enforced as a membership-based permission gate org-wide, not as a requirement that resources live inside the allowed groups.
  • Jobs cost attribution uses the resourceGroupId field in the job payload, not the namespace.
• Copy cleanup: key terms bolded, nested bullets flattened, role names shown as code, creator role labels matched to the UI (Write+, Contributor+).

The enterprise-resource-groups page gets updated screenshot alt text.

---

Note

Low Risk
Documentation-only changes with no runtime or API code; risk is limited to readers following outdated Jobs CLI/API examples if docs were wrong before.

Overview
Updates Hub documentation so Resource Groups org-settings guidance matches the redesigned UI and correct product behavior.

The getting started flow now documents the per-group page with Overview, Resources, Users, and Settings tabs, retaken light/dark screenshots (overview, add-resources modal, auto-include, spend limits, granular access), and clearer image alt text on the enterprise overview page.

Accuracy fixes: Jobs cost attribution uses resourceGroupId (org name stays namespace); Read+ creation excludes no_access org members; granular feature access is described as a membership gate org-wide, not a requirement that resources live in allowed groups. Auto-join and spend limits instructions point to the Settings tab; copy is tightened (bold terms, role labels like Write+/Contributor+).

^{Reviewed by Cursor Bugbot for commit e3dd1b6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-31T18:14:25.959387Z	54d308f	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[HuggingFaceDocBuilderDev]

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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e4ed6491f5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[davanstrien]

Suggested change

	- **Jobs**: pass the resource group's ID as the `resourceGroupId` field when creating a job. See [Bill to a resource group](./jobs-pricing#bill-to-a-resource-group).
	- **Jobs**: set `namespace` to the owning organization and pass the resource group's ID using `resource_group_id` in Python, `--resource-group-id` in the CLI, or `resourceGroupId` in the HTTP request body. See [Bill to a resource group](./jobs-pricing#bill-to-a-resource-group).

[julien-c]

Suggested change

	- **All org members**: check **Include no_access members** to include every member, including members with the `no_access` organization role.
	- **Read+ members only** (default): leave **Include no_access members** unchecked to exclude members with the `no_access` organization role.
	- **All org members** (default): leave **Include no_access members** unchecked to exclude members with the `no_access` organization role.
	- **All org members including no_access**: check **Include no_access members** to include every member, including members with the `no_access` organization role.