Skip to content
All modules Platform & Settings

User Management software for Indian schools

Create and manage users

Feature identity

User Management

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

Example view

User Management in a school workflow

Create and manage users

Platform & Settings
User Management in a school workflow
Platform & Settings
  1. 01
    Required context

    Verified staff identity and assigned role must be confirmed before rollout.

  2. 02
    Supported work

    One-click staff invite with credentials delivered over email + WhatsApp.

  3. 03
    Reviewable result

    Provisioned staff accounts with one-time credential handover, forced first-password change, 2FA and immutable login history.

Example record

User Management

Authorised view
  • One-click staff invite with credentials delivered over email + WhatsApp
  • Unique random temp passwords and a forced first-login password change
  • Mandatory OTP 2FA, or an offline authenticator (TOTP) with backup codes
  • Login history is immutable at the database level
Provisioned staff accounts with one-time credential handover, forced first-password change, 2FA and immutable login history.
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

Staff logins are provisioned, never self-signed-up: the admin creates a user and gets a handover bundle — school code, sign-in link, and a unique random temporary password with a forced change on first sign-in. Permissions resolve fresh on every request, mandatory 2FA guards every login, and the first successful sign-in flips an invite to active.

The school problem

School teams need a dependable way to handle User Management: Create and manage users. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Create and manage users.

  1. One-click staff invite with credentials delivered over email + WhatsApp
  2. Unique random temp passwords and a forced first-login password change
  3. Mandatory OTP 2FA, or an offline authenticator (TOTP) with backup codes
  4. Login history is immutable at the database level

Operational result

What your school gets

Provisioned staff accounts with one-time credential handover, forced first-password change, 2FA and immutable login history.

Access and ownership

Who typically uses it

  • Tenant administrator
  • IT administrator
  • Security administrator
  • School owner

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

  • Verified staff identity and assigned role
  • 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 User Management work on its own?

Role & Permission, Staff Management, Institute Settings, Teacher App 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 User Management?

Verified staff identity and assigned role. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in User Management?

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

See it in your school context

Run user management the connected way.

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