feat(users): Add suspension UI to gsAdmin user details#114354
Merged
Conversation
github-actions
Bot
added
the
Scope: Frontend
dashed
force-pushed
the
aleal/feat/user-suspension-frontend
branch
from
d8e4196 to
799e620
Compare
dashed
force-pushed
the
aleal/feat/user-suspension-frontend
branch
from
799e620 to
4353632
Compare
dashed
force-pushed
the
aleal/feat/user-suspension-frontend
branch
from
4353632 to
181ccad
Compare
dashed
force-pushed
the
aleal/feat/user-suspension-backend
branch
from
682f744 to
ed9790b
Compare
Add Suspend/Unsuspend actions and Suspended badge to the gsAdmin user detail page. Suspended users show a red "Suspended" badge and status. The Reactivate Account action is hidden when a user is suspended, since only unsuspending should be offered first. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Suspend and unsuspend actions now call POST /_admin/users/{userId}/suspend/
instead of PUT /users/{userId}/, enabling admin audit log entries.
Audit params (notes, ticketURL) flow from the confirmation modal to the
endpoint. The suspend action shows a danger-priority confirm modal.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dashed
force-pushed
the
aleal/feat/user-suspension-frontend
branch
from
8174148 to
b55aac0
Compare
dashed
changed the base branch from
aleal/feat/user-suspension-backend
to
master
The commitAuthor and userDetails fixtures were missing the isSuspended default, causing TypeScript errors since the User type requires boolean but the Partial<User> spread made it boolean | undefined.
2 tasks
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
The onError handler used `error.message ?? fallback`, but RequestError.message is always a non-null string so the nullish coalescing operator never reached the user-friendly fallback. Admin users saw raw technical messages like "POST /…/suspend/ 500". Use the hardcoded message directly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
Add Suspend/Unsuspend actions and Suspended badge to the gsAdmin user detail page so admins can manage user suspension from
/_admin/users/:userId/.Actions
PUT /api/0/users/{id}/with{isSuspended: true}.PUT /api/0/users/{id}/with{isSuspended: false}.Status Display
The user overview shows "Suspended", "Active", or "Disabled". A red "Suspended" badge appears next to the user name (can coexist with the "Inactive" badge).
Depends on on #114349 and https://github.com/getsentry/getsentry/pull/20159 (backend logic), and #114328 (migration).