Security at EduOffice.

Every EduOffice user only sees the data and tools their role is permitted to use.

Principals, Admins, Teachers, Parents and Staff each work in their own portal, built around what that role actually needs. An Admin can also grant or restrict individual Staff members' access to specific features one by one — and that permission is checked on the server before the action runs, not just hidden as a button in the interface.

Each institute's data is fully separated from every other institute on EduOffice, enforced at the database level.

Every table holding institute data — students, staff, attendance, fees, results and more — carries database-level access rules tied to that institute. A logged-in user cannot query another institute's records no matter how the request is made; this isn't a rule the app's interface merely enforces, it's enforced by the database itself.

Access to EduOffice always requires a signed-in, authenticated account — there is no public or anonymous access to institute data.

Every portal page checks, on the server, that a valid session exists before showing any data, and sends anyone without one to the login page. Accounts issued with a temporary default password (for example, new Teacher or Parent logins) must be changed to a real password before the account can reach any portal page. An Admin can also deactivate an individual account or turn off an entire role's portal school-wide, and that takes effect immediately.

Sensitive actions are restricted to the roles authorized for them, and that check runs on the server — not only in the interface.

Actions like publishing results, approving payments or admitting a student are gated by a permission check the server runs before the action executes. Turning a specific action on for a Staff account is a deliberate choice made by an Admin, and can be revoked at any time.