Responsibilities
Giving a member of staff a duty — and the rule that stops that becoming an escalation.
A duty is a job somebody does: running the library, the hostel, the stores, being a head of department. It is granted to a person, and it can be taken back or moved.
Why duties rather than roles
Schools do not divide neatly by job title. The person who runs the library is a teacher. Rather than inventing a "librarian-teacher" role, you grant the library duty to the teacher.
Granting a duty is what puts its screen in that person's navigation.
The rule that matters
Nobody can grant a duty that gives more access than they hold themselves. An administrator cannot use delegation to manufacture a wider grant than their own, for themselves or anyone else.
Where the work happens
Operational duties are done in this console, not in the teacher portal — even by a teacher. The console's screens are school-wide where the teacher portal's are section-scoped, and mirroring a module into both would silently widen what "Attendance" means for whoever holds a duty.
Revoking
Revoke here. It takes effect for the person's next session, and it is audited — who revoked what, and when.
Review it
Duties granted for a term and never revoked are how access quietly accumulates. Review the list at the start of each year.
Last updated