Work / Chitragupt / Wiki / Flows
admin-moderates-ca-application
Flowcanonicalverified 2026-06-26
FLOW.ADMIN-MODERATES-CA-APPLICATIONFlow — Admin moderates CA application
Summary
Admin reviews a pending CA application, inspects credentials and risk signals, and approves, requests clarification, or rejects with a 90-day cooldown.
Audience
admin
Entry
admin-dashboard → "CA applications" card.
Steps
| # | Step | Surface | Notes |
|---|---|---|---|
| 1 | Admin dashboard | admin-dashboard | "N CA applications pending" card |
| 2 | List | admin-ca-applications | Bulk queue view |
| 3 | Detail | admin-ca-application-detail | Credentials, AI risk signals, pricing-policy check, references |
| 4a | Approve | admin-ca-application-detail | CA profile goes live; CA receives approval email; downstream of ca-application-onboarding |
| 4b | Request clarification | admin-ca-application-detail | Auto-email asks for specific items (fresh selfie, KYC call, etc.) |
| 4c | Reject | admin-ca-application-detail | CA receives email; 90-day reapply cooldown |
| 5 | Audit log entry | admin-dashboard | Statutory record per 2026-05-30-admin-impersonation-no-reason |
Exit
CA application resolved: approved (live on marketplace) · clarification requested · or rejected with cooldown. Audit log entry written.
Escapes
- Pricing policy violation: routes to ca-portal-pricing correction request; CA returns via clarification path.
- Suspected fraud (risk signals high): admin can escalate; reject + add note to internal block list.
- CA does not respond to clarification: application expires; CA must reapply.
Sources
- .context/wiki/flows/* § "Flow 10 — Admin moderates CA application"
Every project of mine is written down like this.
Read the résumé