All modules HR & Payroll

Staff Management software for Indian schools

Records and role mapping

Feature identity
Staff Management
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Staff Management in a school workflow

HR & Payroll

01
Required context
HR & Payroll enabled for your school (still rolling out school by school) must be confirmed before rollout.
02
Supported work
Directory CRUD with search, department filters and an Employee-360 detail view.
03
Reviewable result
A controlled employee directory with statutory identifiers, masked finance details and a traceable active/deactivated lifecycle.

Example record

Staff Management

Authorised view

Directory CRUD with search, department filters and an Employee-360 detail view
Grant app access in one click — mints a login and delivers credentials over email + WhatsApp
Statutory fields validated server-side: PAN, 12-digit UAN, ESIC, IFSC, Aadhaar-last-4 only
Staff self-service: own profile, payslips and statutory self-completion

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

When the HR & Payroll workspace is enabled for your school (it's still rolling out school by school), maintain a staff directory with departments, designations, auto-generated employee codes (EMP0001) and format checks for India statutory fields such as PAN, UAN, ESIC and IFSC. Bank-account values use protected storage and masked display, while staff with linked history can be deactivated instead of hard-deleted.

The school problem

School teams need a dependable way to handle Staff Management: Records and role mapping. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Records and role mapping.

Directory CRUD with search, department filters and an Employee-360 detail view
Grant app access in one click — mints a login and delivers credentials over email + WhatsApp
Statutory fields validated server-side: PAN, 12-digit UAN, ESIC, IFSC, Aadhaar-last-4 only
Staff self-service: own profile, payslips and statutory self-completion

Operational result

What your school gets

A controlled employee directory with statutory identifiers, masked finance details and a traceable active/deactivated lifecycle.

Access and ownership

Who typically uses it

HR administrator
School administrator
Principal
Employee

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

Still rolling out school by school

Staff lifecycle, leave, compensation and payroll workflows.

HR & Payroll enabled for your school (still rolling out school by school)
Built — enabled school by school; confirm availability for your school
This capability is still rolling out school by school; ask us about availability before you plan it into your rollout.

Flagship workflow deep dive

Staff Directory, Identity & Access

One employee record. One controlled login.

Maintain a staff directory with departments, designations, generated employee codes and server-side format checks for India statutory fields such as PAN, UAN, ESIC and IFSC. App access is granted from the same record, bank values use protected storage with masked display, and staff with linked history are deactivated rather than deleted.

Interactive operating model

From joining record to controlled access

Follow one employee from the directory entry to the login, and to the deactivation that ends it.

Illustrative workflow · no customer data

Stage 1 of 5

Record created

The employee is added with department, designation and a generated employee code.

Control point

The code comes from one per-school counter, so concurrent adds cannot collide.

Evidence retained

Employee record and allocated code.

Core workflows and features

The operational work behind the promise

Directory with real structureKeep employees under departments and designations with search and filters, so a staff list stays usable as the school grows past a printed register.
Generated employee codesAssign a sequential employee code from the school's own counter, so two administrators adding staff at once cannot produce the same code.
Validated statutory fieldsCheck PAN, twelve-digit UAN, ESIC and IFSC formats on the server as they are entered, instead of discovering a malformed value during a filing run.
Protected finance detailsStore bank values in protected storage and show them masked, so a payroll destination is not casually readable from a directory screen.
Employee 360 recordOpen one employee to see their profile, documents, service history and linked workspace records without moving between disconnected screens.
Granted app accessTurn a staff record into a real login in one reviewed action, which links the employee to that login and hands over credentials the person then changes.
Role-based permissionsGive each login only the modules its role needs, so an HR clerk maintaining the directory does not thereby acquire payroll or finance rights.
Document shelf per employeeHold contracts, qualification proofs and identity documents against the employee record, with access following the module the document belongs to.
Staff self-serviceLet a staff member open their own profile, payslips and statutory self-completion, which keeps the HR desk out of routine copy requests.
Deactivate rather than deleteRetire a leaver by deactivating the record so payroll, attendance and document history stay intact and auditable after they have left.

Governed staff records

Access is granted deliberately, and never as a side effect.

Creating a staff record and creating a login are separate, recorded decisions. Directory work never widens someone's access on its own.

Allocate employee codes from one per-school sequential counter that concurrent adds cannot collide on.
Validate PAN, UAN, ESIC and IFSC formats server-side before the value is stored.
Mint a login from an employee record only through the reviewed grant-access action, and link the two identities.
Deliver handover credentials over the school's configured email and messaging channels, subject to their configuration.

Human boundary

A directory entry is not a login. Access is granted by an authorised administrator in a separate, audited action, the temporary credential must be changed by its owner, and an employee whose history is linked elsewhere is deactivated rather than deleted.

Key daily uses

What the school team does here

Add a joiner with their department, designation and statutory identifiers.
Grant, review or withdraw a staff member's app access.
Open an Employee 360 record before a review, transfer or exit conversation.
Complete or correct statutory fields ahead of a payroll or filing cycle.
Deactivate a leaver while preserving their payroll and attendance history.

Used by

HR administrator
School administrator
Principal
Department head
Payroll officer
Employee

Actual access follows the school's plan, role permissions and record scope.

Measurable operating indicators

Metrics to track — not guaranteed ROI

Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.

Statutory completeness

Active employees with valid PAN, UAN, ESIC and bank details against all active employees

Predicts whether the next payroll and filing cycle will run on complete data or on gaps.

Access coverage

Active employees with a linked login against those whose role needs one

Shows who still cannot reach the workspace their job assumes they can use.

Directory hygiene

Records deactivated on exit against recorded leavers

Catches ex-staff who still hold an active record or an active login.

Prerequisites and availability

Confirm the operating context before rollout.

HR & Payroll on a plan that includes it · still rolling out school by school

The HR & Payroll workspace enabled for your school, which is still rolling out school by school.
Departments, designations and the role model your school actually uses, agreed before bulk entry.
An authorised administrator to grant app access, since staff cannot self-register a login.
Configured email and messaging channels if credential handover should reach the employee directly.
Payroll and statutory filing live in the Payroll surface; this module maintains the records they read.

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 adding a staff record create a login?

No. A directory entry and an app login are separate decisions. An authorised administrator grants access in its own recorded action, which links the employee to that login and hands over a temporary credential the person must change.

What happens to a staff member who leaves?

They are deactivated, not deleted. Payroll, attendance and document history stay intact and auditable, and their access is withdrawn — so the record remains provable without leaving an active account behind.

Does Staff Management work on its own?

User Management, Document Management, Staff Attendance, Payroll 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 Staff Management?

Built — enabled school by school; confirm availability for your school. HR & Payroll enabled for your school (still rolling out school by school). This capability is still rolling out school by school; ask us about availability before you plan it into your rollout.

Is AI used in Staff Management?

No AI capability is asserted for Staff Management. 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

Employee & Payroll

See the HR & Payroll workspace Compare plans and commercial costs

See it in your school context

Run staff management the connected way.

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