fix blocker 1 - super admin
This commit is contained in:
@@ -14,18 +14,6 @@ Effort is a rough size, not a schedule: **S** = small/contained, **M** = a real
|
||||
|
||||
## A. The product is broken or unusable
|
||||
|
||||
### Admin can't do anything
|
||||
- **No admin account can perform a single real admin action.** Every super-admin/finance account gets
|
||||
"access denied" on every real admin screen — approving a nurse, moderating a review, processing a refund,
|
||||
running a payout batch, managing tickets, all of it. The permission system only recognizes one hardcoded
|
||||
role name that nothing ever actually assigns. *(Effort: M)*
|
||||
- **On top of that, no demo account holds even that hardcoded role**, so fixing the permission bug alone
|
||||
still leaves nothing to test it with out of the box. *(Effort: S, bundled with the item above)*
|
||||
|
||||
*Why this matters more than it looks: a large share of the other items below — nurse verification,
|
||||
reviews, refunds, payouts, ticket handling — are gated behind this one fix. Fixing admin access is the
|
||||
single highest-leverage thing on this list.*
|
||||
|
||||
### Payments
|
||||
- **A card payment can never actually complete.** The test/demo payment page redirects to a page that
|
||||
doesn't exist. Nothing about the money logic itself is wrong — it's the very last step, handing off to a
|
||||
@@ -81,11 +69,6 @@ Effort is a rough size, not a schedule: **S** = small/contained, **M** = a real
|
||||
reach a state where the nurse can actually be paid for the visits she did complete. The "today's visits"
|
||||
list nurses see is also unfiltered — it shows a nurse's entire history, not just today. *(Effort: M)*
|
||||
|
||||
### Reviews
|
||||
- **A real review can never actually go live.** It gets submitted and saved correctly, but the approval step
|
||||
that would publish it sits behind the broken admin-access problem above, so nothing ever gets un-stuck.
|
||||
*(Effort: S once admin access is fixed)*
|
||||
|
||||
### Catalog / pricing
|
||||
- **Outside of the developer's own local setup, there are zero service categories or pricing options
|
||||
configured at all**, and there is no admin page to add them — only direct database editing. Deployed as-is,
|
||||
|
||||
Reference in New Issue
Block a user