Operations
Hand it to your team without handing over the keys
You are not the person who will spend all day in this. Coordinators, instructors and assistants are. The console assumes that from the start.
- Roles
- 5
- Editable email templates
- 24
- Broadcast segments
- 10
- Data access
- CSV + Postgres
01
Five roles, and an approval queue
Instructors should be able to publish without an owner unblocking every change — and without being able to see the whole payment ledger.
- Owner, admin, instructor, contributor and student
- New instructors publish into a review queue rather than onto the live site
- Payment records and student contact details permission-gated
- Per-person approval requirement you can switch off once trust is earned
02
Every automated email is yours
The messages your platform sends are part of your brand. All of them should be editable, and none of them should surprise you.
- Every transactional email editable, with a test send
- Reset any template back to the default
- Attach documents like a welcome pack or a syllabus
- Sent from your domain, not a shared platform address
03
Broadcast to a list that means something
Not a newsletter blast. Segments built from the states your business actually cares about.
- Accepted but unpaid, waitlisted, enrolled, finished, never applied
- Recipient count shown before anything sends
- CSV export from every table in the product
- Direct Postgres access for your own reporting
Bring your coordinator to the call
They will find the gaps faster than you will, and their questions are the ones worth answering.