Can a single course have multiple teachers?

Yes. The primary owner stays the headline teacher (signs the certificate, shown in the hero), and you can add any number of co-instructors with full edit access. Modules can also have their own owners — Module 1 by Faculty A, Module 2 by Faculty B.

What does the invite email look like?

Workspace-branded — ' invited you to '. The accept-invite link lands the recipient inside your branded portal (not the platform default), where they pick a password and land in the dashboard. The link is good for 7 days.

Can the same teacher work across multiple workspaces?

Yes — a teacher invited at workspace A and workspace B keeps a separate profile in each (different bio, colors, course list) but uses the same email identity. The invite UX surfaces this so admins aren't surprised when they see 'already on the platform'.

Multi-instructor courses + admins

Teaching is a team sport.

Solo-creator platforms force a single-instructor mental model on people who run real schools, agencies, and cohorts. We don't. Invite as many co-teachers and admins as you want, assign per-module owners, and let the same teacher work across multiple workspaces without creating duplicate accounts.

Open Faculty Read the guide

Branded invite emails
Strong-password onboarding
Co-teach + per-module owners
Multi-tenant accounts

An invite flow you can actually trust

Most platforms send a vague "reset your password" email when an admin invites a new teacher. We send a real invite email — workspace-branded, with the inviter's name, a 7-day link, and a clean accept-invite landing.

Workspace-branded email

Subject reads '<inviter> invited you to <workspace>'. The CTA lands on your tenant's branded accept-invite page, not the platform default.

Strong by default

Passwords scored by dropbox/zxcvbn — minimum 'good' (3/4). Passwords containing the invitee's name, email, or workspace name score lower; generator output passes immediately.

Tenant-scoped tokens

Invite tokens carry the workspace slug in a signed claim. A token issued for workspace A can't be used inside workspace B — even if someone swaps the URL slug.

Co-instructors

Add any number of co-teachers to a course. The primary owner stays the headline teacher; co-instructors get full edit access. Toggle from a chip rail on the course's Curriculum tab.

Per-module ownership

Module 1 owned by Faculty A, Module 2 by Faculty B. Each module gets its own optional owner; the page falls back to the course owner when not set.

Multi-tenant teachers

The same teacher can be a faculty member at multiple workspaces. We don't create duplicate accounts — we link by email and keep each workspace's profile separate.

Profiles that look good on the public site

The fields you collect on the faculty form render straight onto the public instructor card on every course they teach, plus the /instructors showcase page. No separate "public profile" data model to maintain.

Core identity

Full name + email (locked after invite)
WhatsApp number (required, E.164 validated)
Role — instructor or admin
Avatar + cover image
Short bio

Online presence (optional)

Personal website / portfolio
LinkedIn
X / Twitter
Instagram
YouTube
GitHub

All links rendered with rel="nofollow noopener noreferrer" on public pages.

90-second onboarding for new teachers

1
Admin opens /dashboard/faculty and fills the form. We send a workspace-branded email.
2
Recipient clicks the link, lands inside your branded portal at /p/<tenant>/accept-invite.
3
They pick a password (zxcvbn-validated). The strength meter gives live feedback until they hit 'good' or better.
4
We provision the user in your workspace and sign them in. Instructors + admins land on /dashboard; students land on /p/<tenant>.

Build a teaching team

No per-seat charges hidden in fine print. Invite as many co-teachers as your workspace needs.

Invite your first teacher Faculty guide