What this module is for
Use Schoolixa AI features safely for draft content, insights, and automation support while keeping humans in control.
Prerequisites
- AI module permission assigned
- AI service configured server-side
- Source module data available for the selected draft task
Main screens
Step-by-step workflows
Check AI readiness
- Open AI Analytics & Automation.
- Run or review readiness status.
- Confirm the AI service is available before using generator buttons.
Use AI as a draft assistant
- Open a supported module such as homework, lesson plans, notices, or question papers.
- Click AI Generator where available.
- Review generated draft content.
- Edit and approve manually before using it in official records.
Operational detail
Permission checkpoints
- 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.
Field guidance
Use readiness checks to confirm the server-side AI bridge is configured and reachable before using generators.
AI Generator buttons should be visually consistent and pulse subtly to show optional draft assistance.
Provide minimal task context and avoid sensitive student, staff, credential, or payment data unless the workflow explicitly permits safe summarization.
Review, edit, and approve generated text before saving it into official module records.
AI requests should keep safe metadata for operational review without exposing provider prompts, keys, payloads, or raw responses.
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.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.