2.2 KiB
2.2 KiB
type, title, description, tags, timestamp, story_id, status
| type | title | description | tags | timestamp | story_id | status | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| User Story | Manage users as an administrator | Authorized operators search users and maintain their names, linked accounts, primaries, and Discord nicknames. |
|
2026-08-01T22:34:31Z | US-013 | verified |
User Story
As an administrator, I want to manage a user's identity and Minecraft accounts, so that support issues can be resolved without direct database access.
Acceptance Criteria
- Administrators can search by preferred name, Discord username or ID, Minecraft username, or UUID.
- Search results show onboarding state, primary username, and active account count.
- A user detail view shows Discord display name, username, guild nickname, immutable ID, active accounts, groups, recent events, and recent IP observations.
- Administrators can update the preferred name and synchronize Discord.
- Administrators can add Mojang-verified accounts or explicitly override an unverified username.
- Administrators can remove an account only after a visible confirmation step.
- Removing a primary account selects a replacement or falls back to the preferred-name nickname.
- Administrators can set a new primary account and automatically update Discord.
- Every action rechecks role and account ownership and records the acting administrator.
- Discord failures do not falsely persist the requested name, primary, or removal change.
Implementation
apps/web/src/app/admin/(console)/users/page.tsxapps/web/src/app/admin/(console)/users/[userId]/page.tsxapps/web/src/app/admin/(console)/users/actions.ts
Validation
Nickname fallback behavior is tested in packages/minecraft/test/minecraft.test.ts. Privileged routes pass TypeScript, lint, Semgrep, and production build checks.