All modules Automation & Compliance
Automations software for Indian schools
40 ready-made rules and a visual builder — every run audited.
Feature identity
Automations
An illustration, not a screenshot. The interactive example below shows what this capability actually does.
Example view
Automation & ComplianceAutomations in a school workflow
40 ready-made rules and a visual builder — every run audited.
Product scope
What it does
When Automation is included in your plan and switched on, the library contains 40 starter rules for fee and invoice reminders, absence WhatsApps, attendance-shortfall alerts, at-risk interventions and document-expiry sweeps. Rules start disabled. Build or edit a rule on the visual canvas and simulate it before enabling; side-effects come only from a fixed catalogue of reviewed actions.
The school problem
School teams need a dependable way to handle Automations: 40 ready-made rules and a visual builder — every run audited. The required records, assigned roles and review boundary must remain explicit.
Day-to-day work
How your school uses it day to day
40 ready-made rules and a visual builder — every run audited.
- 40 starter rules, off by default — you choose what runs
- No-code if-this-then-that with nested branching; simulate before enabling
- Version history with one-click rollback
- Per-run, per-step audit drill-down — no open code execution
Operational result
What your school gets
A disabled-by-default library of 40 starter rules plus a simulated, versioned rule builder and per-step run evidence.
Access and ownership
Who typically uses it
- Tenant administrator
- Process owner
- Module manager
- Automation reviewer
- Auditor
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
Included from Premium
No-code trigger/action rules with simulation, version history and per-run audit evidence.
- A plan that includes Automation, plus configured triggers/actions and an authorised decision to enable each rule
- 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.
- Task ManagementRecurring SOPs, proof, and review
- Fee ReminderHuman-reviewed overdue-payment nudges
- Auto Absence AlertTrigger on threshold
- Document ManagementStore and retrieve files
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 Automations work on its own?
Task Management, Fee Reminder, Auto Absence Alert, Document Management 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 Automations?
A plan that includes Automation, plus configured triggers/actions and an authorised decision to enable each rule. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.
Is AI used in Automations?
No AI capability is asserted for Automations. Its documented work remains controlled by school records, roles and permissions.
How do we confirm the plan and implementation scope?
Automations is included from Premium in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.
See it in your school context
Run automations the connected way.
See how this workflow fits your school's current records, roles, plan and rollout requirements.