Teacher-Scoped Attendance and Grading by Class Level

Plenty of school software hides buttons a teacher "shouldn't" see and calls that security. Hiding a button in the interface does nothing to stop a request sent directly to the server — real access control has to be enforced where the data actually lives, not just where it is displayed.

Scoped where it counts

On mySmartAccessCard, every teacher is assigned to specific class levels and subjects through the school's course setup. When a teacher marks attendance or records a result, the server checks that assignment before saving anything — a teacher can only act on students in a level they are actually assigned to teach. This is enforced on the backend, so it holds even if someone tries to bypass the app's own interface.

Why this matters for a real school

• No accidental cross-contamination — a Primary 4 teacher covering a colleague cannot accidentally overwrite Primary 6 results.
• Clean accountability — every attendance mark and every grade is traceable to a teacher who was actually authorised to enter it.
• Substitute and multi-subject teachers are still fully supported — scoping is based on assignment, not a rigid one-teacher-one-class rule.

Extended to per-teacher class times

The same scoping model lets an individual teacher override the school's default resumption and closing time for their own class — which then drives that teacher's own late/absent cutoffs for attendance. A JSS1 class that resumes earlier than the rest of the school does not get flagged late by a schedule that was never actually theirs.