Submissions

Submissions is the admin surface for every public-submitted record across the platform — Calendar event submissions, Opportunity submissions, contact-form messages, partnership inquiries. All flow into a single unified queue with module-aware routing, so a triage operator can clear submissions across modules without context-switching admin URLs.

Admin surfaces

• /founder-account/admin/submissions — unified queue. Each row: submission type, submitter contact, target module, submission timestamp, status (new / in-review / accepted / rejected / requested-info).
• Quick actions on each row open the module-specific verification surface — clicking "Verify" on a Calendar event submission jumps to /founder-account/admin/calendar/:id/edit.
• /founder-account/admin/submissions/contact — contact-form messages. Separate sub-queue because these don’t map to a module entity, just need a human response.
• /founder-account/admin/submissions/partnerships — partnership inquiries. Handled by business-development team, not editorial. Separate audit trail.

Submitter communication

• Every status transition sends a templated email to the submitter’s email — accepted, rejected (with reason), needs-info (with what’s missing).
• Email templates are bilingual; submitter receives the email in their submission locale (the locale the submit form was rendered in).
• Submitter can reply to the email; replies are threaded into the submission record (admin sees the conversation history).