Roles, Approvals and Audit History
Role-based access decides who sees and changes what. Approval steps and a traceable record of important actions are configured alongside the modules a college implements.
Access follows the role
A college handles personal records, marks, fees and approvals across many offices, so access has to follow the role of the person and not the machine they use. The system defines roles first, and every module then reads them.
Role-based access
Approval steps
A traceable history
What the college decides
The college decides which roles exist and which approvals apply. The system enforces those choices and does not make them. Roles and approval steps are configured during implementation with the people who own each process.
Frequently asked questions
Can a head of department see only their own department?
Yes, where the role is set that way. Access can be limited to a department, a programme or a section.
Can a new role be added later?
Yes. Roles are configured and can be added or adjusted after launch.
Is every change recorded?
Important actions such as marks changes, concessions and approvals are recorded. The list of recorded actions is agreed during implementation.
Can an approval chain have more than one step?
Yes. Some requests need a single reviewer, and others pass through several offices in order.
Tell us what you need.
Send a short brief and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
