Skip to documentation content
Schoolixa Documentation
Exams, Fees & Reports

AI Analytics

Use Schoolixa AI features safely for draft content, insights, and automation support while keeping humans in control.

Audience
Admins, teachers, coordinators, and permitted AI users
Last reviewed
September 2, 2026

Overview

Use Schoolixa AI features safely for draft content, insights, and automation support while keeping humans in control.

Before you start

  • AI module permission assigned
  • AI service configured server-side
  • Source module data available for the selected draft task

Main screens

AI Control Center Readiness Check AI Generator Buttons Draft Review Areas

Step-by-step workflows

1

Check AI readiness

  1. Open AI Analytics & Automation.
  2. Run or review readiness status.
  3. Confirm the AI service is available before using generator buttons.
2

Use AI as a draft assistant

  1. Open a supported module such as homework, lesson plans, notices, or question papers.
  2. Click AI Generator where available.
  3. Review generated draft content.
  4. Edit and approve manually before using it in official records.

Operational detail

Permission requirements

  • AI Analytics and each AI Generator button require explicit AI permission plus the source module permission.
  • Browser and mobile clients must never call FastAPI or OpenAI directly; all AI requests go through the Schoolixa server.
  • AI output is draft-only and cannot publish, approve, mark attendance, change fees, alter marks, or promote students.

Readiness status

Use readiness checks to confirm the server-side AI bridge is configured and reachable before using generators.

Generator buttons

AI Generator buttons should be visually consistent and pulse subtly to show optional draft assistance.

Prompt inputs

Provide minimal task context and avoid sensitive student, staff, credential, or payment data unless the workflow explicitly permits safe summarization.

Draft review

Review, edit, and approve generated text before saving it into official module records.

Audit behavior

AI requests should keep safe metadata for operational review without exposing provider prompts, keys, payloads, or raw responses.

Security boundary

AI cannot be used as a shortcut for lifecycle decisions in attendance, fees, results, promotion, or publication.

Validation and system feedback
  • AI routes validate authentication, permission, CSRF, request shape, and source module eligibility.
  • AI provider details, keys, prompts, payloads, and raw responses must not appear in the browser.
  • Draft-only behavior must remain intact even when AI succeeds.
  • Unavailable AI service should show a controlled error, not a raw provider or server trace.
Common mistakes to avoid
  • Using AI output without human review.
  • Trying to generate official marks, attendance, or fee changes through AI.
  • Calling the AI service directly from browser JavaScript or Flutter.
  • Pasting private documents, credentials, or identifiers into a prompt.

Safe use

Keep documentation and support privacy-safe

These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.

  • Using AI output without human review.
  • Trying to generate official marks, attendance, or fee changes through AI.
  • Calling the AI service directly from browser JavaScript or Flutter.
  • Pasting private documents, credentials, or identifiers into a prompt.