Notifications and System
Platform-side announcements, email, logs, and user management. Channel callbacks and merchant notification push belong to the trade domain — see Trade Management.
Notification Center
The announcement list from the recipient's perspective:
- The top action bar shows the unread count and Mark all as read (effective after confirmation);
- Rows: unread red dot, importance tag (important in red), pinned marker, title (bold when unread), time;
- Opening a detail marks it read automatically; the body renders as rich text. The unread state of the workbench announcements card follows along.
Announcement Management
From the sender's perspective:
- List: filter by title and status (draft / published / offline); cards show the tag, title, effective time (empty = effective immediately), and last modified time;
- Edit: title, importance (normal / important), pinned or not, effective / expiry time (expiry must be later than effective), body (Markdown);
- Status flow: draft → (publish) → published → (take offline) → offline; both publish and take-offline ask for a second confirmation. Published announcements are pushed to the notification centers and workbench announcement cards of all clients.
Email
Email Templates
One scenario = two language slots (Chinese / English), edited and saved independently:
- Five slots per language: subject, title, content (required); tip, footer (optional);
- Template variables are shown as tags; tap one to append it to the end of the content (no cursor positioning on the phone);
- Helpers: Fill Defaults (restores the official default copy, not persisted), Preview (the rendered view), Test Send (sends a real email to a given address to verify the result);
- Customized templates can be reset per language back to the defaults.
Send Records
- Filter by recipient mailbox, status (sending / success / failed), and business type (test / manual / password reset / email binding and change notices, etc.);
- Detail: recipient mailbox, subject, business type, status, error info, retry count; the body supports a rendered / source toggle;
- Failed records can be resent or deleted.
Logs
All three logs can be queried on the phone:
| Log | Filters | Card highlights |
|---|---|---|
| Login logs | account, result (success / failure) | method and terminal, IP, failure reason, time |
| Operation logs | account, result | operation module, failure reason, time; the detail includes request method / URL / params |
| API logs | API path or title, result | path, over 3 seconds flagged red as "slow call", failure reason; the detail includes the merchant and full messages |
For login anomalies, check the failure reason in the login logs first; for open API integration issues, check the messages and latency in the API logs.
Platform Users
The platform's own operations accounts (accounts signing in to the admin panel, distinct from merchant users):
- List: name, account, administrator marker, status dot (normal / locked / banned); long-press a card to open the action panel;
- Detail actions: edit, reset password (the system generates a random initial password, shown only once), assign role (single role; built-in roles carry markers), lock / ban (from the normal state), unlock (from an abnormal state); status actions are not offered for the administrator account;
- Create: name, account, password, etc. — the same flow as creating a merchant user.
Related Links
- Notifications and Email (Web): the Web panel in detail
- Merchant Management: the boundary between merchant users and platform users
- Admin App Feature Map