Page body
What this tab shows
Players / Inbox is the message-history tab for one player. It lets operators review previously sent notifications and manage the player's inbox state without leaving the workspace.
When to use it
Use this tab when you need to:
- confirm whether a player received a notification
- review unread vs read inbox state
- search sent messages by title or content
- resend, mark as read, or delete inbox records
How to read it
The tab is built around a split view:
- message list on the left
- message preview on the right
On mobile, the FE switches between a list view and a preview view instead of keeping both panes visible at once.
Operators can narrow the list with read-state filters, notification-type filters, and a text search field. Search matches the message title and the rendered English content.
The preview pane shows:
- title
- sender identity (
customFrom, admin creator name, orSystem) - notification type
- priority
- delivered timestamp
- optional read timestamp
- optional image/avatar
- rendered message content
Known caveats
- This tab shows inbox records and notification history. It is not the same thing as the
Send To Inboxmodal, which is the mutation flow for creating a new player message. All,Unread, andReadfilters change the inbox result set, whileSystem,Personal, andBroadcastfilters change the notification source type.- The FE loads this tab with
includeDeleted=true, so soft-deleted rows can still be visible in history and show aDeletedbadge in the sender line. DeleteandBulk Deleteare soft-delete operations onuser_notifications.deleted_at, not hard removal from the notification tables.Resend Messagedoes not update the old inbox row. It creates a new notification throughPOST /api/admin/notificationswith the selected message content andisResend=true.- The FE allows bulk delete and resend operations from the message list, but these actions should still be treated as notification-management operations, not chat support history.
Verification status
- status:
verified_backend - last verified:
2026-04-18 - note: user-notification list, read/delete mutations, and resend creation flow are traced through the inbox hooks and notification controller/services.