Skip to content
All modules Leadership & AnalyticsDedicated Aira capability

Aira Assistant governed AI for Indian schools

Ask permission-scoped questions about supported school records by text or voice.

Feature identity

Aira Assistant

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

Example view

Aira Assistant in a school workflow

Ask permission-scoped questions about supported school records by text or voice.

Leadership & Analytics
Dedicated Aira capability

Aira Assistant

Ask permission-scoped questions about supported school records by text or voice.

ScopeOnly supported, permission-checked school context
  1. Required contextA plan that includes the Aira AI assistant, plus credits and permissions for each requested source must be confirmed before rollout.
  2. Supported workSupported answers include student counts, fee outstanding, today's attendance and open tasks.
  3. Reviewable resultPermission-scoped answers over supported school records plus reviewable actions that execute only after the relevant confirmation.
Governed resultPermission-scoped answers over supported school records plus reviewable actions that execute only after the relevant confirmation.
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 voice is configured, ask supported questions by text or voice in 11 supported languages and hear the answer read aloud. Aira uses a fixed set of permission-checked tools, so each person can request only the supported records their role is allowed to reach. The default AI router pattern-redacts common identifiers; name removal depends on the calling flow supplying the known values.

The school problem

School teams need a dependable way to handle Aira Assistant: Ask permission-scoped questions about supported school records by text or voice. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Ask permission-scoped questions about supported school records by text or voice.

  1. Supported answers include student counts, fee outstanding, today's attendance and open tasks
  2. Voice in and read-aloud out when the voice provider is configured
  3. Safe write-actions: Aira proposes, a human confirms, then it executes
  4. Included with the Aira assistant tier · metered as credits

Operational result

What your school gets

Permission-scoped answers over supported school records plus reviewable actions that execute only after the relevant confirmation.

Access and ownership

Who typically uses it

  • School owner
  • Principal
  • School administrator
  • Accountant
  • Teacher

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

Permission-scoped Aira questions and supported actions that require human confirmation.

  • A plan that includes the Aira AI assistant, plus credits and permissions for each requested source
  • Configured voice provider for voice input/read-aloud
  • Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Aira — Permission-Scoped School Assistant

Answers your role is already allowed to see.

Ask supported questions about your school's records by text, and by voice in eleven supported languages where a voice provider is configured. Aira reaches records through a fixed set of permission-checked tools, so each person can only request what their role already permits, and any write action is proposed for a human to confirm before it executes.

Interactive operating model

From question to a scoped, confirmed answer

Follow one question through the permission, redaction and confirmation gates it must pass.

Illustrative workflow · no customer data

Stage 1 of 5

Question asked

A signed-in person asks by text, or by voice where a provider is configured.

Control point

The asker's identity and role travel with the request; there is no anonymous mode.

Evidence retained

Question, asking identity and channel.

Core workflows and features

The operational work behind the promise

  1. Ask in plain languagePut the question the way you would ask a colleague, instead of learning where a number lives in a reporting screen you use twice a term.
  2. A fixed tool surfaceAnswer from a defined set of read tools — student counts, fee outstanding, today's attendance, open tasks — rather than an open query over the database.
  3. Permission checked per requestRe-check the asking person's permissions on every request, so a role change takes effect immediately rather than at the next sign-in.
  4. Tenant-bounded answersKeep every answer inside the asking school's own data, enforced in the database and not only in the application layer.
  5. Redaction before the modelRoute model calls through one funnel that pattern-redacts common identifiers such as phone numbers and email addresses before the prompt leaves the platform. Name removal depends on the calling workflow, and permissions and source records stay authoritative.
  6. Voice in, answer outSpeak the question and hear the answer read back in the chosen language, where the school has configured a voice provider.
  7. Propose, confirm, executeHave Aira propose a supported action and execute it only after an authorised person confirms it, so nothing is changed by a conversation alone.
  8. Grounded in the school's own helpAnswer how-to questions from the published help material, so guidance matches the product the school is actually using.
  9. Metered as creditsMeter usage as credits against the school's plan, so AI consumption is visible and bounded rather than an invisible running cost.
  10. Health data firewalledExclude health, infirmary, wellbeing and counselling records from the assistant's reach entirely, as special-category data that never enters this surface.
  11. Degrades honestlySay plainly when a question is outside the supported tools, rather than inventing a confident answer from nothing.

Governed AI over permissioned records

Aira can only reach what you can already reach.

Aira is bounded by the same permissions, tenancy and record scoping as the rest of the workspace. It reads through fixed tools, and its write path is a proposal a person confirms.

  • Resolve each question through a fixed set of read tools rather than free-form database access.
  • Re-check the asking person's permissions on every request, so revoked access applies immediately.
  • Redact identifiers through one model funnel before any prompt leaves the platform.
  • Propose a supported write action and execute it only after an authorised person confirms.

Human boundary

Aira is not an administrator. It cannot exceed the asking person's permissions, cannot reach another school's data, and cannot reach health, infirmary, wellbeing or counselling records at all. Material actions execute only after a human confirmation, and every AI call is metered against the school's credits.

Key daily uses

What the school team does here

  1. Ask for today's attendance or this month's outstanding fees without opening a report.
  2. Check open tasks or a supported roll-up before a morning meeting.
  3. Ask a how-to question and get an answer grounded in the published help material.
  4. Ask by voice in a supported language and hear the answer read back.
  5. Review and confirm an action Aira has proposed.

Used by

  • School owner
  • Principal
  • School administrator
  • Accountant
  • Teacher
  • Academic coordinator

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.

Answered scope

Questions resolved through a supported tool against questions asked

Shows where the assistant genuinely helps and where a person still needs the full screen.

Credit consumption

Credits metered per active user per month

Keeps AI cost visible against the plan's allowance instead of accumulating unseen.

Confirmed actions

Proposed actions a person confirmed against actions proposed

Evidences that the human confirmation step is real and being exercised.

Prerequisites and availability

Confirm the operating context before rollout.

Aira AI assistant on a plan that includes it · credits and per-source permissions apply

  • A plan that includes the Aira assistant, plus available credits for the school.
  • Permissions configured per person, since an answer never exceeds what the asker may already see.
  • A configured voice provider if voice input and read-aloud should be available.
  • Answers cover the supported tool surface; Aira is not an open query interface over every table.
  • Health, infirmary, wellbeing and counselling records are excluded from this surface by design.

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.

Can Aira see more than the person asking?

No. Permissions are re-checked on every request and answers stay inside the asking school's own data. Health, infirmary, wellbeing and counselling records are excluded from this surface entirely, whatever the asker's role.

Can Aira change something in our school by itself?

No. Aira reads through a fixed set of tools, and a supported write action is proposed for an authorised person to confirm before it executes. A conversation on its own never changes a record.

Does Aira Assistant work on its own?

Talk to Your Data, Voice Aira, Automations, Task 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 Aira Assistant?

A plan that includes the Aira AI assistant, plus credits and permissions for each requested source. Configured voice provider for voice input/read-aloud. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Aira Assistant?

Dedicated Aira capability. Aira supports only the reviewed actions listed on this page, and authorised people remain responsible for confirming material actions.

How do we confirm the plan and implementation scope?

Aira Assistant is included from Premium in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

See the Leadership & Analytics workspace Compare plans and commercial costs

See it in your school context

Run aira assistant the connected way.

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

You control analytics.

Necessary storage keeps sign-in and saved preferences working. Optional analytics and session replay stay off until you allow them, and our event contract excludes names, contact details and student records. Cookie Policy