Skip to main content

Center Users, Roles, and Permissions

Center owners usually need a simple permissions model that can grow over time.

Center roles example

Suggested roles

RoleMain permissions
Center ownerfull access, billing, provider setup, staff management
Adminmanage users, classes, schedules, reports
Teachermanage classes, attendance, meetings, course episodes
Studentjoin classes, watch episodes, view assignments

Sample permission matrix

ActionOwnerAdminTeacherStudent
Connect Zoom/JitsiYesOptionalNoNo
Invite adminsYesYesNoNo
Add teachersYesYesNoNo
Add studentsYesYesOptionalNo
Create class scheduleYesYesYesNo
Start meetingYesYesYesNo
Watch episodeYesYesYesYes

Add center admins

Open:

Center Settings → Team → Admins → Invite Admin

Suggested fields:

  • full name
  • work email
  • mobile number
  • role
  • branch access

Add teachers

For teachers, store extra fields:

  • department
  • subjects
  • assigned classes
  • preferred meeting provider
  • bio and avatar

Add students

Recommended student fields:

  • student code
  • guardian contact
  • level or grade
  • branch
  • enrolled classes
  • active/inactive status

Permission design tips

  • assign permissions to roles first
  • add custom overrides only when necessary
  • log who changed provider keys and schedules
  • keep billing and secrets limited to owners

Example internal role payload

{
"role": "teacher",
"permissions": [
"class.view",
"class.edit",
"schedule.create",
"meeting.start",
"episode.upload"
]
}

Next step

Read Class schedules and meeting planning for the daily operating flow.