Students
—
Real server data required
ড্যাশবোর্ড
সেশন ও বর্তমান access state যাচাই হচ্ছে…
Role: verifying…
Authenticated session যাচাই হয়েছে; server-authoritative role/scope contract সংযুক্ত না হওয়া পর্যন্ত privileged actions fail-closed থাকবে।
Attendance
—
No fabricated production KPI
Pending Reviews
—
Awaiting authorized backend query
Payments
—
Financial values stay server-authoritative
Core Modules
Student 360°
Multi-year academic, attendance, payment and promotion history with scope controls.
Attendance
Daily + subject-wise attendance with independent authorization scopes.
Exams & Results
Draft → Review → Publish → Lock, with policy-gated transitions.
Payments
Gateway + Cash Receive, idempotency and audited payment lifecycle.
Documents & QR
Official document generation/verification with server-authoritative canonical data.
Notifications
In-app → Web Push → Email → optional channels; never blocks Core transactions.
System Health
System health is observer-only. Provider/database state remains authoritative and is not replaced by this UI.
Student 360° Profile
Academic + attendance + payments + promotion history এখানে দেখানো হবে কেবল authorized server query-এর ফল হিসেবে। Teacher scope বর্তমান academic year + class + section + subject-এর বাইরে historical data পাবে না।
Backend query/RLS contract এখনো সংযুক্ত হয়নি। কোনো mock student record দেখানো হচ্ছে না।
Daily
Subject-wise
Draft
Published
Correction
Class Daily Attendance
Authorized only through the designated class-teacher scope:
academic_year + class + section + designated_class_teacher
Subject Attendance
Authorized only through the assigned-subject scope:
academic_year + class + section + subject
Published attendance must be locked; corrections follow Original → Correction → Reason → Actor → Timestamp → Approval → Audit.
Attendance backend/RLS/RPC এখনো সংযুক্ত হয়নি।
Draft
Review
Publish
Lock
Examination & Result Workflow
Final Submit → Review. Pre-Publish resubmission replaces only the pending submission artifact while preserving the superseded change in audit. Published/Locked data uses the formal correction workflow.
Transition-authority matrix is an open institutional policy decision. This UI will not invent who may perform Draft → Review, Review → Publish, or Publish → Lock.
Academic engine + transition RPC + RLS are not yet connected.
Online Gateway
Provider reference + internal transaction ID + duplicate settlement prevention.
Cash Receive
Online/server-authoritative final commit; no financial draft is persisted in browser storage.
Refund/reversal/chargeback remains out of Core until an approved institutional policy exists.
Payment tables/RPC/RLS/provider callbacks are not yet connected.
Official Documents & QR Verification
Official marksheets/admit cards are Core capabilities.
- Canonical server-authoritative payload
- Document registry + unique document ID + hash
- Opaque public verification identifier
- QR as enhancement, not hard dependency
- Server-side cryptographic signing
Public verification exposes only minimum necessary information.
Official document generation + verification backend is not yet connected.
In-app
Primary $0 channel.
Web Push
Browser-native $0 channel.
Resend free quota, verified at implementation time.
SMS / WhatsApp
Optional/provider-dependent fallback channels.
Notification failure must never block the underlying Core transaction.
Notification queue / Edge Function / Web Push subscription storage are not yet connected.
Admission
Institutional admission rules, girls-only eligibility, religion-locking and ID-generation rules must be enforced server-side.
Admission forms/RPC/RLS are not yet connected.
Bulk Import
Chunked SheetJS parsing → row validation → staging → atomic execution → audit.
Demo Mode
Strictly isolated from production data, metrics, financial records, academic results, documents and audit history.
Routine Builder
Admin-only scheduling with database-enforced conflict prevention for teacher/room/class/duplicate-slot conflicts.
Routine/assignment schema + transactional conflict protection are not yet connected.
Security Center
Super Admin only after authoritative backend role verification and required AAL2 assurance.
Security Settings
MFA/AAL2, privileged authorization and application-configured rate limits.
System Health
Observer-only provider/infrastructure status.
Service-role/secret credentials must remain server-side. This frontend never receives a secret key.