Trust & security
Trust.
Most school software can't tell you who changed a number, or when — ScholaRise can, for every meaningful action, across the whole platform.
- Audit log
- Roles
- Isolation
- Provisioning
- DPDP-aware
Every change, on the record.
- P. Mehra Accountantfee.concession.update Student #SR-4471 · Term II₹0 ₹8,50009:41:07 10.2.14.6HIGH
- A. Verma Class teachermarks.entry.submit Class IX-B · Mathematicsdraft submitted09:38:52 10.2.31.9NOTICE
- System Provisioningworkspace.account.suspend staff · r.singh@school.eduactive suspended09:34:18 —NOTICE
- S. Iyer Front officevault.document.share TC series · doc #TC-1182private link · 7-day expiry09:30:44 10.2.14.2INFO
- K. Rao Principalrole.permission.revoke role · Examination Clerkresults.publish denied09:22:05 10.2.10.1HIGH
Rendered in the ScholaRise app palette · figures illustrative — the structure and computed fields are real.
The question no demo wants to be asked.
From the boardroom
A receipt is queried, a mark disputed, a document sent somewhere it shouldn't have been — and the principal turns to the system to ask the only question that matters in that moment: who changed this, and when? In most school software the honest answer is a shrug, and that shrug is what a trustee quietly weighs when they sign — not the colour of the dashboard, but the accountability of the record. ScholaRise was built so the answer is never a shrug: every meaningful action leaves a trace you can read, tied to the person who took it, with the before and the after both kept. We frame none of this as fear — it's simply the difference between software that demos well and software a careful institution can actually be run on.
-
The Vault
A secure home for the school's documents: organised by series and tags, access granted by role, share links that expire (with a reminder before they do), AI help to sort and review, and a full trail on every file.
-
An audit log nobody can edit
Every meaningful action is recorded — who, what, when, from where, and the before-and-after of whatever changed. The platform can always answer the one question that matters: who did this, and when?
-
Granular access control
100+ fine-grained permissions — by role, by campus, and locked by default: if nothing grants access, there is none. The same rules govern the screens, the apps and the Sol AI agent, identically.
-
Workspace provisioning
Student and staff Google Workspace accounts, created automatically — sorted into the right groups, moved in bulk, and switched off the moment someone transfers out or leaves.
-
Realtime sync
Every open screen stays current on its own — it notices when it's fallen behind and quietly catches up — so no administrator ever acts on a number that went stale ten minutes ago.
-
Each school walled off
Built so every trust's campuses and academic years are cleanly separated. A branch's data, and a year's data, stay exactly where they belong — not by habit or good intentions, but by design.
-
01 / 03
The same model that lets Sol act safely. Sol, the platform's AI agent, runs through the exact same permission checks a person does — by campus, locked by default, the same 100+ permissions. It can't see a number someone in its seat couldn't see, or change one they couldn't change. The trust layer isn't beside the AI; it's underneath it.
-
02 / 03
Correct across campuses, years, and roles. Every record is pinned to a school, a campus and a year, so a trust running several campuses across overlapping years gets one clean picture with no bleed between them. The audit trail spans all of it — web, iOS, and Android — from one source of record.
-
03 / 03
The foundation for a governance conversation. We don't claim certifications we don't hold. What we can say plainly: the system is built to support good data-governance practice, and it's DPDP-aware in its handling of personal data. When your board is ready to formalise that conversation, the engineering underneath is already there to build on.
The principle
Trust isn't a feature you bolt on. It's the layer everything else stands on.
See ScholaRise
in your school.
A real walkthrough with someone who actually runs a school — we'll map what fits your campus today and what's worth phasing in over the next year.
The walkthrough
- Length
- 30 minutes, no slides
- Run by
- Someone who runs a school
- Available
- Across India · web, iOS & Android
- Audit coverage
- Every action
- Permissions
- 100+, locked by default
- Isolation
- Tenant · branch · session
- Posture
- DPDP-aware