What this module is for
Use the Reports & BI hub to review operational metrics and open permission-aware report links across Schoolixa modules.
Prerequisites
- Relevant module permissions assigned
- Current session selected where reports are session-specific
- Report data available in source modules
Main screens
Step-by-step workflows
Read operational snapshot
- Open Reports & BI.
- Review live summary cards for students, staff, attendance, fee, hostel, inventory, library, and report areas.
- Use the refreshed timestamp to understand when the snapshot was loaded.
Open a report
- Find the report area in the catalog.
- Open only reports visible to your permission set.
- Apply filters on the destination report page.
- Export only where the report supports export.
Operational detail
Permission checkpoints
- Reports & BI shows only report areas and links allowed by the current user permissions.
- Opening a report link still requires the destination module permission.
- Exports should follow the same permission and filter rules as the on-screen report.
Field guidance
Reports that depend on academic data should default to the active session and retain selected session filters.
Use live counts to identify broad operational status, not as a replacement for detailed reconciliation reports.
The catalog groups reports by academic, finance, exam, staff, assets, library, hostel, visitor, and other areas.
Apply date, class, section, status, or module-specific filters on the destination report page before export.
Export only the filtered report data needed for the task and avoid sharing files with unnecessary personal information.
Use refresh to reload the snapshot after operational activity such as attendance marking or fee collection.
Validation and system feedback
- Permission filtering on the hub does not replace server-side checks on destination report routes.
- Counts must be school scoped and session scoped where the source module requires it.
- Report links should not expose raw IDs in the browser.
- Exports should not bypass filters or include unauthorized module data.
Common mistakes to avoid
- Treating snapshot counts as audited financial reconciliation.
- Exporting broad reports when a narrow date or class filter is enough.
- Expecting hidden report areas to be accessible by direct URL.
- Sharing exported files without removing sensitive student or staff information.
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.