Roles, permissions and audit log

Role-based access and an audit log your school can rely on

Give every user exactly the access their role needs — teachers see their classes, accountants see fees, parents see their own children. Pair permissions with an activity log so important changes such as marks edits or fee adjustments remain reviewable later.

For school owners, principals and administrators responsible for data access and accountability.

Concept illustration of role rows with permission toggles beside a shield and padlock representing controlled school data access.
Illustrative workflow using example labels, not a product screenshot or a promise of a particular screen layout.

From setup to a reviewable record

01

Map roles to responsibilities

List who in your school needs which records, then review the available roles against that list. Resist granting broad admin access for convenience.

02

Apply and test permissions

Assign roles and verify with a test account that each user sees only what they should. Check sensitive areas such as fees, marks and guardian contacts first.

03

Review the activity log

Use the activity log to review who changed what and when for important records. Agree which events your leadership checks and how often.

What to check in your demo

  • Log in with a test teacher account and confirm restricted areas are hidden.
  • Change a sample record and find the change in the activity log.
  • Review how parent access is limited to their own children's records.

Availability and setup requirements

This page describes role-based access and activity logging. It does not promise custom role builders for every permission combination, legal-grade audit certification or external SIEM integrations. Confirm available roles, log retention and export options in a demo.

Feature availability depends on the product, configured package and current interface. Confirm the screens, setup and permissions your team will use in a guided demo. A feature described here is not a promise that it is bundled into every plan.

Review access and infrastructure features

Frequently asked questions

Can parents see other students' data?

The described model limits parents to their own children. Verify this with a test parent account during your demo.

Which actions appear in the activity log?

Review the logged events against the actions your school considers sensitive. Confirm retention and who may view the log.

Can we create fully custom roles?

Do not assume unlimited custom roles. Review the available roles and permission granularity against your requirement before rollout.

Explore connected workflows

See how this fits your school

Share your institution size and the workflow you want to review. No student or parent records are needed to request a demo.