Center Users, Roles, and Permissions
Center owners usually need a simple permissions model that can grow over time.
Suggested roles
| Role | Main permissions |
|---|---|
| Center owner | full access, billing, provider setup, staff management |
| Admin | manage users, classes, schedules, reports |
| Teacher | manage classes, attendance, meetings, course episodes |
| Student | join classes, watch episodes, view assignments |
Sample permission matrix
| Action | Owner | Admin | Teacher | Student |
|---|---|---|---|---|
| Connect Zoom/Jitsi | Yes | Optional | No | No |
| Invite admins | Yes | Yes | No | No |
| Add teachers | Yes | Yes | No | No |
| Add students | Yes | Yes | Optional | No |
| Create class schedule | Yes | Yes | Yes | No |
| Start meeting | Yes | Yes | Yes | No |
| Watch episode | Yes | Yes | Yes | Yes |
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.