Access control

Role-based access control where your school writes its own roles

Most software ships three roles. NQ School lets you write your own. Every screen and action is a named permission, and a role is simply a set of them, enforced on the server and not just hidden on screen.

One platform, every module Flat ₹10,000 a year
Access control

Most software ships three roles. YOURS WRITES ITS OWN.

Every screen and action is a named permission, and a role is simply a set of them. Pick a role and watch the switches change.

+ Build your own
PR
Principal
0of 12
allowed
    Enforced on the server, not just hidden on screen.
    Why it matters

    Access control, without the paperwork.

    A school is full of people who should see very different things. The accountant should not see marks, the class teacher should not see payroll, and a parent should see their own children and nobody else’s.

    Instead of forcing those people into a handful of fixed roles, NQ School lets you build exactly the roles you need, such as an Exam Coordinator who runs the entire exam cycle and nothing else.

    What you get

    What Access control gives your school

    Permissions, not job titles

    Every screen and action is a named permission. A role is a set of them.

    Build your own roles

    Write a role for the way your school actually works, then assign it to the right people.

    Scoped access

    A class teacher gets their own sections and papers. A parent gets their own children only.

    Enforced on the server

    Access is checked where the data lives, so hiding a button is never the only protection.

    Separation between schools

    A principal has full authority inside their school and no reach into any other school on the platform.

    Activity is logged

    Access is controlled by role and activity is logged, so you can answer who did what.

    How it works

    From start to finish in four steps.

    1. Start from the permissions

      Review the named permissions, such as marking attendance, entering marks and collecting fees.

    2. Write a role

      Combine permissions into a role that matches a real job in your school.

    3. Assign it

      Give the role to the right staff, with scope where it applies.

    4. Add roles as you grow

      Write a new role whenever your school needs one, such as a new coordinator post.

    FAQ

    Questions about ACCESS CONTROL.

    Straight answers, before you ask.

    Still have a question? Talk to us. We reply within one working day.

    Yes. A role is a set of named permissions, and you can build as many as your school needs, such as an Exam Coordinator.

    Yes. A class teacher is scoped to their own sections and papers, and the roster they see is the roster they teach.

    No. Parents see their own children only, enforced at the query.

    Yes. Permissions are enforced on the server and not only hidden on screen.

    Book a demo

    See it with your own school in mind.

    A demo runs about forty minutes and is built around your school’s size and what you run today.

    Book a demo