Every multi-instructor platform eventually meets the same four problems: instructors editing what is not theirs, inconsistent quality reaching the catalogue, revenue disputes built on missing numbers, and admin bottlenecks when one person must approve everything. Ukkera's team & permissions model was designed against precisely these failure modes — this is how to configure it.
The five-role template #
- Owner: full control — platform settings, instructor contracts, payout rules
- Instructor: create and edit own courses only — sees own analytics, never other instructors' data
- Reviewer: quality gate — approves course publication against your standards checklist
- Finance: payout visibility — revenue, refunds and instructor shares without content access
- Support: learner-facing help scoped to course content, not platform settings
Content groups as governance rails #
Permissions say who can act; groups say where. Mapping content groups to catalogue categories gives each instructor a lane, each reviewer a domain, and each analytics view a clean scope. When an instructor crosses into a new category, it is a deliberate permission change — not an accident of a shared folder. That discipline is what lets a marketplace scale from five instructors to fifty without governance debt.
A marketplace operations lead: 'We grew to 40 instructors without a single content-rights dispute. Our old platform couldn't even tell us who edited what.'