Inspiration
If you've lived in a dorm, you know the routine. Your sink leaks, you submit a ticket, and then nothing happens. You call housing, housing tells you to call maintenance, and maintenance can't find your request. The fix itself is usually small. Most of the time gets lost in the handoffs between offices that can't see each other's work. We wanted to build something that fixes the handoffs, not just the ticket form
What it does
Tiger Ops is a campus operations hub, modeled on Grambling State University's real departments and buildings.
Students sign up with their @gsumail.gram.edu email, report a problem in their room, and watch it move from triage to done. They get progress updates, but staff-only notes stay hidden. Staff get invite-only accounts. A department head chooses the role, the halls, which features to switch on, and how long the access lasts. A contractor's account can end on its own after 30 days, for example. Each person sees only their own slice. A plumber sees the jobs assigned to them, not student records. The housing director can see and assign work across Housing and the maintenance team under it. The president sees totals, not individual students' requests. Sensitive offices like the Health Center don't pass their records up the chain by default. Maps use the official campus map (all 65 numbered buildings in their real positions), with clickable 2D floor plans for each residence hall. An AI assistant answers questions in plain English and asks for confirmation before it does anything.
How I built it
The front end is plain JavaScript, with SVG for the maps and floor plans. Behind it is a Node server and a Postgres schema designed for Supabase. The access rules live in the database itself (row-level security), so the browser is never trusted to filter records. While developing, we run that same schema on PGlite, a version of Postgres that runs inside Node, and we can move to Supabase without rewriting it.
Challenges we ran into
Permissions were harder than any feature. "Directors can see everything under them" sounds simple until counseling records are under them too. We wrote a test that checks the database rules against the app's rules for every role and every work order, and it caught a real bug in the database rules that would have quietly let some checks through.
Accomplishments that we're proud of
Every building and department is grounded in Grambling's public pages. Anything we assumed is labeled as a pilot model. Invitations can't be used to hand out more access than the person sending them has.
What we learned
Most campus problems are coordination problems. Good permissions aren't about locking people out. They give each person exactly what they need to finish their part.
What's next for Uni-Verse
Connect to Supabase and Grambling's real systems. Replace our modeled floor plans with official ones. Add 3D building views. Run a pilot with one residence hall.
Built With
- agentic
- campus
- mangement
