2 Commits

Author	SHA1	Message	Date
Omair Saleh	b477dc30d1	Role-based access control: guards on all critical APIs + redirects ... INTEGRATION AUDIT — Fixed all gaps: 1. LOGIN REDIRECT - Community leaders → /dashboard/community (not /dashboard) - Fetches session after login to check role before redirect - Auth0 callback still goes to /dashboard (handled by #2) 2. DASHBOARD HOME REDIRECT - If role === community_leader or volunteer → router.replace(/community) - Prevents them from seeing the admin home page 3. API ROLE GUARDS (server-side) New: src/lib/roles.ts — permission matrix: - settings.write: super_admin, org_admin only - pledges.write: super_admin, org_admin only (status changes) - events.create: super_admin, org_admin only - imports.upload: super_admin, org_admin only (bank statements) - links.create: super_admin, org_admin, community_leader (they can create) - pledges.read: everyone except volunteer - dashboard.read: everyone except volunteer New: requirePermission() in session.ts Applied to: - PATCH /api/settings → settings.write - PUT /api/settings → settings.write - PATCH /api/pledges/[id] → pledges.write - POST /api/events → events.create - POST /api/imports/bank-statement → imports.upload Community leader attempting these gets 403 'Admin access required' 4. LAYOUT NAV (already done in previous commit) - community_leader sees: My Community, Share Links, Reports - No Money, No Settings, No 'New Appeal' button WHAT COMMUNITY LEADER CAN DO: ✓ View /dashboard/community (their scoped dashboard) ✓ View /dashboard/collect (share links — they can create new links) ✓ View /dashboard/reports (financial summary) ✓ Create QR sources / links (POST /api/events/[id]/qr) ✓ Read pledges and dashboard data WHAT COMMUNITY LEADER CANNOT DO: ✗ Change pledge statuses (PATCH /api/pledges/[id] → 403) ✗ Change settings (PATCH/PUT /api/settings → 403) ✗ Create appeals (POST /api/events → 403) ✗ Upload bank statements (POST /api/imports/bank-statement → 403) ✗ Manage team (POST/PATCH/DELETE /api/team → 403, already guarded) ✗ See /dashboard/money, /dashboard/settings (not in nav, home redirects)	2026-03-04 21:58:25 +08:00
Omair Saleh	9c7990e05c	Reconciliation embedded in Money — no more separate page ... The reconcile feature was hidden behind a text link at the bottom of the Money page. That's backwards. Reconciliation IS the Money page. Aaisha's actual thought process: 1. People pledged 2. Some say they paid 3. 'Did the money actually arrive?' → opens bank website, downloads CSV 4. 'Let me match it' → THIS SHOULD BE RIGHT HERE, not behind a link 5. '8 out of 10 matched' → pledges auto-move to 'received' Changes: - Full bank statement upload area is NOW embedded directly in /dashboard/money With icon, description, drop zone — always visible, not a link - When CSV is selected: file name + detected bank format shown inline Column mapping is collapsed by default (auto-detected) but expandable - 'Match payments' button is blue, full-width, prominent - Results appear INLINE below the upload area: - Summary stats (gap-px grid): rows, incoming, matched, possible, auto-confirmed - Green success banner when pledges are auto-confirmed - Full match results table with confidence icons - 'Upload another' button to reset - After matching: dashboard data auto-refreshes to show updated pledge statuses - 'Said they paid' section now says 'Upload a bank statement above to confirm' instead of linking to a separate page - /dashboard/reconcile now redirects to /dashboard/money (backward compat) - Contextual sections (confirm/nudge) hide when match results are showing to avoid visual clutter Architecture is now: Stats → MATCH PAYMENTS → Confirm these → Need a nudge → All pledges table Not: Stats → table → small link at bottom → navigate away → separate page	2026-03-04 21:35:23 +08:00