Roles and Permissions

Purpose

Controls who can do what. Example: allow teachers to mark attendance but not delete invoices.

Who uses it

Super Admin, School Admin (for their institution's custom roles).

Depends on

Modules seeded in system (done during installation).

Plain language

• Role = job title bucket (Teacher, Accountant)
• Permission = single action (e.g. invoice.create = can create invoices)

Step-by-step — Create custom role "Senior Accountant"

• Menu → Roles → Add Role
• Name: Senior Accountant, Institution: Green Valley
• Open Assign Permissions
• Enable: Invoices (view, create), Payments (view, create), Fee Structures (view)
• Disable: Student delete, Settings manage
• Save.
• Assign this role to user finance@gvis.edu.ci in Staff module.

Common questions

Q: Teacher sees "403 Forbidden".

A: Their role lacks permission for that page. School Admin adds the permission.