Exams, Fees & Reports

Reports & BI

Use the Reports & BI hub to review operational metrics and open permission-aware report links across Schoolixa modules.

Audience: School owners, admins, accountants, coordinators, and permitted staff
Last reviewed: September 2, 2026

Overview

Use the Reports & BI hub to review operational metrics and open permission-aware report links across Schoolixa modules.

Before you start

Relevant module permissions assigned
Current session selected where reports are session-specific
Report data available in source modules

Main screens

Reports & BI Hub Operational Snapshot Report Catalog Module Report Links

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 requirements

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.

Session context

Reports that depend on academic data should default to the active session and retain selected session filters.

Snapshot cards

Use live counts to identify broad operational status, not as a replacement for detailed reconciliation reports.

Report catalog

The catalog groups reports by academic, finance, exam, staff, assets, library, hostel, visitor, and other areas.

Filters

Apply date, class, section, status, or module-specific filters on the destination report page before export.

Export

Export only the filtered report data needed for the task and avoid sharing files with unnecessary personal information.

Refresh

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.

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.

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.