Troubleshooting (Admin)
Nội dung này hiện chưa có sẵn bằng ngôn ngữ của bạn.
Executive summary
Section titled “Executive summary”This page collects common admin app issues: sign-in, 403 vs visible menu, empty lists when filters or modules do not match data, notifications (API-backed inbox), and placeholder KPIs. It points to auth, roles, and tenancy docs. For browser errors from admin/vendor web, see Client events & UI errors.
Goals and non-goals
Section titled “Goals and non-goals”| Goals | Non-goals |
|---|---|
| Fast self-serve triage before tickets | Replace backend logs or DB inspection |
| Clarify UI vs API enforcement | Guarantee resolution for misconfigured infrastructure |
Current platform behavior
Section titled “Current platform behavior”- Sidebar does not hide unauthorized areas; APIs return 403 when
modulesor store/tenant rules disallow the action. - Notifications load from the API (Notifications); auth self-serve may be incomplete (Sign-in).
Sequence: happy path
Section titled “Sequence: happy path”- User hits an issue → check sign-in type (Staff vs Super) → network/JWT.
- If 403 → verify role modules (Roles).
- If empty data → verify filters, store, and
modules(Tenancy — stores and outlets).
Security and operations
Section titled “Security and operations”- Do not share JWT or reset links in chat; rotate credentials via approved process.
Test scenarios (UAT / QA)
Section titled “Test scenarios (UAT / QA)”| ID | Scenario | Expected |
|---|---|---|
| T1 | Intentionally wrong password | Clear failure, no partial session |
| T2 | User missing module | 403 on API, doc explains why |
| T3 | Zone admin vs master | Data scope differs as documented |
Cannot sign in
Section titled “Cannot sign in”- Confirm you chose the correct admin type on the login screen (Staff vs Super), matching how the account was provisioned.
- Check API base URL and network errors (browser devtools). See Authentication.
- Registration / forgot password / OTP flows in the admin SPA are not connected to real APIs yet (Sign-in and account); use operational processes to reset access.
Menu item vs API access
Section titled “Menu item vs API access”The sidebar lists management, product, and inventory entries for all users; authorization is enforced on the backend. If a route loads but APIs return 403, your JWT modules array may omit the feature key (for example catalog item). See Roles.
Empty lists or “wrong” data
Section titled “Empty lists or “wrong” data”- Role / module limits: if lists are empty, confirm the signed-in admin has the right
moduleskeys and that filters (store, vendor, date range) match the data you expect. See Tenancy — stores and outlets. - Stores / vendors stat tiles may show — while the table still loads; some KPIs are not wired to overview endpoints yet.
Notifications
Section titled “Notifications”The notifications page reads admin_notifications for the signed-in admin (Notifications). It is an in-app inbox, not a substitute for monitoring or on-call alerting.
Who to contact
Section titled “Who to contact”Use your organization’s internal support or engineering channel for account creation, zone changes, and role updates.