Clarify GetUser response fields by account role - #5232
Merged
lennessyy merged 5 commits intoSep 4, 2026
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
@LutaoX is attempting to deploy a commit to the Temporal Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The duplicate user permissions matrix remains misleading without the new response-scope caveat.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Clarifies role-dependent user API responses and Namespace assignment permissions.
Changes:
- Adds authorization caveats for
GetUserandGetUsers. - Adds
GetUserNamespaceAssignmentsto the Namespace Admin matrix. - Links the operation in the Custom Role table.
File summaries
| File | Description |
|---|---|
docs/cloud/manage-access/permissions-reference.mdx |
Updates permission matrices and authorization guidance. |
docs/cloud/manage-access/_custom_role_permissions_table.mdx |
Links the Namespace assignment operation. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
lennessyy
approved these changes
Sep 4, 2026
lennessyy
enabled auto-merge (squash)
September 4, 2026 18:27
lennessyy
disabled auto-merge
September 4, 2026 18:27
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
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
Why
The permissions matrix previously implied that every role can inspect another user's account role and Namespace permissions. Non-admin callers get HTTP 200 with those fields omitted. Customers (including codec-server least-privilege setups) were hitting this gap.
Test plan
‡footnote on GetUser and GetUsers links to User authorization behaviorMade with Cursor