Roles and Permissions
Learn what each user role is responsible for.
Educan uses roles to guide people to the right workspace.
Permissions then control what each person can see or do inside that workspace.
Role Summary
| Role | Workspace | Main responsibility |
|---|---|---|
| Super Admin | Internal | Full application access, including user approvals, Finance, and access administration. |
| Staff | Internal | Operational Admin, Reception, or Accounting responsibilities. |
| Support | Support | Handle support conversations. |
| Teacher | Teacher | Teaching, assignments, gradebook, and results. |
| Student | Student | Student learning activity. |
| Parent | Parent | View information for linked students. |
| Consultant | Consultant | Bring and support local students, agents, offers, and commissions. |
| Agent | Agent | Bring students and track related commission information. |
Super Admin
The existing admin account type is presented as Super Admin. It retains full application access and is not the lower-privilege Operational Admin Staff type.
They usually handle:
- users
- staff access
- academic setup
- finance setup
- admissions setup
- commission setup
Super Admin accounts are created through the dedicated administrative command, not the ordinary create-user page. The application identity does not require Django's superuser flag.
Staff
Staff use the internal workspace.
Staff creation requires one of three Staff types:
| Staff type | Responsibility | Important limits |
|---|---|---|
| Operational Admin | Academic catalog, placement, enrollment, sessions, grading, attendance, trips, services, and inventory. | No Finance, admissions cases, commissions, user approvals, staff creation, access administration, deletion, or service payment/price overrides. |
| Reception | Necessary student information, read-only attendance, and trip registrations. | No attendance editing, trip setup/lifecycle management, account support, Finance, or materials handling. |
| Accounting | Student financial positions and routine charges, payments, allocations, statements, and reports. | No deletion, payment reversal, charge approval, coverage overrides, discounts, or Finance configuration. |
The selected Staff type appears in the profile header. Authorized users can change it with a three-option dialog; doing so resets additional access. Advanced access combinations remain available from the profile's Access tab.
See Create a Staff User for setup and verification steps.
Support
Support users handle conversations from users who need help.
They usually work with:
- inbox
- messages
- attachments
- conversation status
Teacher
Teachers focus on classroom and academic work.
They may use:
- assignments
- gradebook
- results
- placement information
Student
Students use the student workspace after they are ready for study.
They may need registration, placement, enrollment, or an international case before reaching the normal student workspace.
Parent
Parents view information for students linked to them.
They do not manage operational records.
Consultant
Consultants help bring and support local students.
They may work with:
- students
- agents
- offer letters
- programs
- sessions
- commissions
Agent
Agents help bring students to the institution.
They mainly work with:
- their students
- commission information
An agent may need approval before normal workspace actions are available.
Access Checks
When a user cannot see a page or action, check:
- Does the user have the correct role?
- Is the user account ready?
- Does the user have the needed access?
- Is the record connected to that user or workspace?