UniAct

A deployed multi-platform university operating system for web, mobile, desktop, and AI-assisted learning.

UniAct is a complete digital platform for universities. It connects university onboarding, tenant administration, academic setup, student and staff accounts, schedules, enrollment, attendance, grades, transcripts, learning groups, announcements, analytics, and AI study support into one ecosystem.

The project is currently deployed:

• Book a demo: www.uniact.website
• Manage platform tenants: public.uniact.website
• Try sample tenants: anu.uniact.website or alexu.uniact.website

UniAct is designed as a multi-university platform. One backend serves many universities, while each university keeps its own isolated academic workspace.

In simple terms:

flowchart LR
    User["User opens a UniAct URL"] --> Host["Hostname decides context"]
    Host --> Public["public.uniact.website: platform management"]
    Host --> Tenant["anu.uniact.website / alexu.uniact.website: university tenant"]
    Tenant --> Header["Tenant identity is sent to backend"]
    Header --> Schema["Backend switches to the correct university schema"]
    Schema --> Apps["Web, mobile, desktop, and AI features use the same source of truth"]

The backend handles:

• Tenant creation and schema preparation.
• Authentication and role-based access.
• Super admin, root admin, staff, and student account lifecycle.
• University branding and public tenant profiles.
• Faculties, programs, courses, semesters, rooms, schedules, and enrollment windows.
• Attendance, grades, transcripts, announcements, learning groups, and analytics.
• Background jobs, WebSocket updates, file/media handling, and email verification.
• AI material sync between learning groups and the AI service.

This architecture makes UniAct feel like a dedicated system for each university, while still being managed from one platform.

The super admin area is available at public.uniact.website. It is the control center for managing the platform itself.

Super admins can manage:

• Universities and tenant availability.
• Other super admins.
• Tenant root admins.
• Root admin assignment with Brevo-powered verification email.
• Root admin status, password resets, and verification resend.
• Public tenant records and tenant-level visibility.

This is useful for an organization that wants to onboard more than one university without deploying a separate system for every institution.

Inside a university tenant, users log in with only email and password. UniAct reads the user's university context and assigned role, then sends them to the correct experience.

flowchart TD
    Login["Email + password"] --> Identity["Backend verifies tenant and identity"]
    Identity --> Role["Role is resolved"]
    Role --> Admin["Root/Admin pages"]
    Role --> Staff["Staff/Faculty pages"]
    Role --> Student["Student pages"]
    Role --> Alumni["Alumni and career pages where enabled"]

This keeps the experience simple for users. They do not need to choose a separate product or portal after login. The platform adapts to who they are.

Each university tenant can have root admins who manage the university's academic and operational setup.

Root admins can work with:

• University identity, settings, branding, and public profile.
• Faculties, programs, academic levels, regulations, courses, and prerequisites.
• Rooms, schedules, timetabling, semesters, and enrollment windows.
• Staff and student records, including bulk student import.
• Role and permission management.
• Attendance oversight and grade management.
• Announcements, analytics, and administrative dashboards.

For a university, the root admin is the person who turns UniAct from a platform into a working academic environment.

Staff and faculty members get web tools for the teaching workflows they use most often:

• Dashboard for assigned academic activity.
• Attendance management for courses and sessions.
• Grades and assessments.
• Learning groups and course communication.
• AI assistant access for course materials.
• Profile and account management.

The mobile_flutter repository gives staff a Flutter experience for mobile and desktop. It is especially useful for classroom workflows such as attendance, where speed and offline tolerance matter.

The Flutter repository also includes a GitHub Actions workflow for producing Windows builds, so reviewers and testers can download and try the desktop version from the repository releases/actions output.

Students get a focused academic experience:

• Dashboard with academic status and upcoming activity.
• Course enrollment during configured enrollment windows.
• Timetable and class schedule.
• Attendance visibility.
• Learning groups, posts, files, and assignments.
• Transcript and academic progress.
• AI assistant support connected to learning material.
• Alumni and career features where enabled.

On Flutter, students can access key university workflows from a phone or desktop app. The mobile app is designed around practical daily usage: timetable checks, attendance-related flows, learning groups, transcript access, and tenant-branded dashboards.

UniAct includes an AI feature hub connected to academic material. The AI system is designed to support learning groups, uploaded materials, and document-grounded help.

AI capabilities include:

• Document upload and indexing.
• Retrieval-augmented chat over learning material.
• Direct answer generation from course content.
• Summaries for long documents.
• Practice exams and question generation.
• Mind map generation.
• Search and study areas.
• Learning-group material sync from the main backend.

The goal is not to replace staff. The goal is to help staff and admins turn real course materials into faster study support, better content navigation, and richer learning experiences.

flowchart TD
    Backend["Multi-tenant backend"] --> Web["Web frontend"]
    Backend --> Flutter["Flutter mobile / desktop"]
    Backend --> Public["Public portal"]
    Backend --> AI["AI service"]
    Web --> Roles["Super admin, root admin, staff, student"]
    Flutter --> Daily["Staff and student daily workflows"]
    AI --> Materials["Course-material intelligence"]

UniAct is split into four repositories so each part can evolve cleanly, but they are designed as one product:

• The backend is the source of truth.
• The web frontend gives the richest management experience.
• The Flutter app gives mobile and desktop access for staff and students.
• The AI service adds document intelligence and study support.

• One ecosystem for platform owners, universities, staff, and students.
• Real multi-tenant architecture with tenant-specific URLs and isolated university data.
• Deployed public portal and sample tenants.
• Role-aware login that routes each user to the right experience.
• Cross-platform delivery: web, mobile, desktop, and AI.
• Offline-capable Flutter attendance workflows.
• AI features grounded in actual uploaded academic material.
• Built around real university operations, not only demo screens.

Start here:

• www.uniact.website to book a demo.
• public.uniact.website to see tenant/platform management.
• anu.uniact.website to view a sample university tenant.
• alexu.uniact.website to view another sample tenant.

UniAct is built to make university operations easier to manage, easier to understand, and easier to access from the device each user already has.