SHAMEL
University operations, one connected system
SHAMEL connects attendance, identity verification, academic scheduling, reporting, and role-based operations across a browser workspace and a Flutter mobile application.
Product overview
SHAMEL organizes daily academic work around five defined roles: system administration, college coordination, teaching, student self-service, and gate operations. Each role sees a focused interface while working against the same institutional records and API.
Two platforms
A full browser workspace for university-wide administration, college-scoped coordination, teaching workflows, student services, and gate monitoring.
A role-aware Android application built for fast access to schedules, dashboards, reports, people, gate records, and authenticated university data.
How they work together
Gate and lecture events enter through browser or mobile workflows.
Authentication and role scope decide what each user can access.
Both clients use the Django API and institutional data model.
Dashboards, warnings, reports, and approvals reflect the same records.
Source-verified architecture. Live production connectivity is not claimed by this website.
Who it serves
Start with the operational role, then connect the workflow, outcome, and available evidence.
Coordinate university-wide records, permissions, reports, exports, and audit history.
Manage schedules, sessions, attendance, student records, and college-scoped work.
Support self-service, identity checks, entry decisions, and operational follow-up across web and mobile.
Complete feature inventory
Every item below maps to an implemented route, data model, API endpoint, or Flutter screen. Planned and fixture-only functions are excluded.
Common questions
The documented source covers administration, college coordination, teaching, student self-service, and gate operations. Exact permissions remain deployment-specific.
The feature inventory, screens, and architecture are source-verified. This showcase does not claim live production connectivity, customer tenancy, or third-party certification.
University teams evaluating connected attendance, scheduling, role-based operations, identity workflows, and institution-controlled deployment can request a walkthrough.
Product video
The longest verified product film in the project: a 50-second tour built from real SHAMEL interfaces and source-backed architecture.
SHAMEL connects university operations across attendance, identity verification, academic scheduling, reporting, and role-based workflows. The web platform and Flutter app use the same institutional records and API. This showcase documents source-verified architecture; live production connectivity is not claimed here.
Real product UI
The selected evidence set was visually reviewed before publication. Permission prompts, device launchers, black frames, and duplicate states were excluded.
Security, storage, integrations & ownership
Role-based access, bearer-token mobile authentication, audit records, login protection, and scoped data access are implemented in the source.
The deployment supports PostgreSQL for the server and SQLite-based local or edge operation. Biometric templates are stored as embeddings rather than raw identity claims.
Django REST endpoints connect the web and Flutter clients; Channels supports real-time updates; export routes produce CSV, Excel, and PDF reports.
SHAMEL is designed for institution-controlled deployment. This website does not claim third-party certifications or provider guarantees that are absent from the project evidence.
SHAMEL
Explore the real interfaces, product film, and verified capability inventory above.
Return to overview Request a walkthrough