All modules Platform & Settings

Role & Permission software for Indian schools

Granular access control

Feature identity
Role & Permission
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Role & Permission in a school workflow

Platform & Settings

01
Required context
Defined user accounts and role responsibilities must be confirmed before rollout.
02
Supported work
Module × action permissions per role, with tenant-level role grants.
03
Reviewable result
An auditable module-and-action access model with record scope and separation-of-duties boundaries enforced on requests.

Example record

Role & Permission

Authorised view

Module × action permissions per role, with tenant-level role grants
Separation of duties built in: requester ≠ approver on refunds, concessions, leave and payroll
Classroom teachers are record-scoped to only the sections they teach
Permission changes apply instantly — no re-login required

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Access is layered, not flat: role permissions, your plan's included features, tenant isolation and record-level section scoping are all checked on every request — and permission changes take effect immediately, because they resolve fresh per request instead of living in a stale token. Payroll is deliberately split from HR, so an HR clerk can edit the directory but can't touch pay.

The school problem

School teams need a dependable way to handle Role & Permission: Granular access control. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Granular access control.

Module × action permissions per role, with tenant-level role grants
Separation of duties built in: requester ≠ approver on refunds, concessions, leave and payroll
Classroom teachers are record-scoped to only the sections they teach
Permission changes apply instantly — no re-login required

Operational result

What your school gets

An auditable module-and-action access model with record scope and separation-of-duties boundaries enforced on requests.

Access and ownership

Who typically uses it

Tenant administrator
Security administrator
School owner
Principal

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Platform & Settings catalogue capability

Defined user accounts and role responsibilities
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does Role & Permission work on its own?

User Management, Approval Workflow, Teacher Mapping, Institute Settings are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Role & Permission?

Defined user accounts and role responsibilities. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Role & Permission?

No AI capability is asserted for Role & Permission. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

Related evaluation guides

See the Platform & Settings workspace Compare plans and commercial costs

See it in your school context

Run role & permission the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.