docs: document Hub API custom role assignment for members and teams - #25996
Open
akristen wants to merge 2 commits into
Open
docs: document Hub API custom role assignment for members and teams#25996akristen wants to merge 2 commits into
akristen wants to merge 2 commits into
Conversation
The public OpenAPI spec listed only core roles for member PUT and omitted team PATCH role, even though the API already accepts custom role names. Co-authored-by: Cursor <cursoragent@cursor.com>
Live member responses already return Editor; the documented enum only listed Owner, Member, and Invitee. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
akristen
requested review from
a team and
gmondello
and removed request for
a team
September 1, 2026 17:04
akristen
marked this pull request as ready for review
September 1, 2026 20:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PUTroleaccepts a custom role name, not onlyowner|editor|member.roleon teamPATCH(core or custom role name) and onorg_groupso the PATCH 200 can include the assigned role.Editortoorg_member.role(title case). Live responses already return it; the old enum was Owner / Member / Invitee only.Test plan
PM must confirm before merge:
rolestill a core value (Owner/Editor/Member), or is it the custom role name? If it is the custom name, drop theorg_member.roleenum in a follow-up and describe a string (core or custom name). If it stays a core value, this PR's enum (Owner|Editor|Member|Invitee) is enough.editor); response stays title case (Editor). Confirm that split is real.org_group.roleis present and is the value just set (core or custom name).