Update from code changes: document OAuth group claims

[mintlify]

Summary

Document OAuth token claims as an alternative to the Info API for group-based access control, including opt-in delimiter behavior. See server PR #7262.

Changes

• Explain source, groupsClaim, and groupsDelimiter configuration.
• Document string splitting, whitespace trimming, empty-segment handling, array behavior, and delimiter caveats.
• Update the English, Spanish, French, and Chinese authentication pages.

---

Note

Low Risk
Documentation-only changes to authentication setup guides; no application or security logic is modified.

Overview
Documents OAuth token claims as an alternative to the Info API URL for group-based access control on private docs sites.

The OAuth section now explains configuring source (id_token or access_token), groupsClaim, and optional groupsDelimiter (1–4 characters), including how string claims are split, whitespace is trimmed, empty segments are ignored, and array claims are handled. Info API URL copy is softened so it is one option for groups, not the only path; the optional user-info step is retitled to focus on group access via the Info API approach.

The same OAuth updates land in English, Spanish, French, and Chinese authentication-setup pages. Spanish, French, and Chinese also wrap major tab subsections in <div id="..."> anchors for deep linking. The Chinese page description frontmatter is expanded to mention OAuth token claims and Info API.

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

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify	🟢 Ready	View Preview	Aug 5, 2026, 11:01 PM

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
tomee	🟢 Ready	View Preview	Aug 5, 2026, 11:01 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.