EMS-143: Fix authentication and improve auditorium experience for all user roles

docker-compose.yaml

@@ -61,6 +61,8 @@ services:
       args:
         - DATABASE_URL=postgresql://admin:password@event-service-db:5432/event_db
     container_name: event-service
+    environment:
+      - TZ=America/Chicago
     env_file:
       ./ems-services/event-service/.env.production
     networks:
@@ -132,6 +134,11 @@ services:
     container_name: speaker-service
     env_file:
       ./ems-services/speaker-service/.env.production
+    environment:
+      - RABBITMQ_URL=amqp://rabbitmq:5672
+      - UPLOAD_DIR=/app/uploads
+    volumes:
+      - speaker-uploads:/app/uploads  # Persistent storage for uploaded materials
     networks:
       - event-net
     depends_on:
@@ -237,5 +244,6 @@ volumes:
   booking-service-data:
   feedback-service-data:
   speaker-service-data:
+  speaker-uploads:  # Persistent storage for speaker uploaded materials
   rabbitmq_data:
   rabbitmq_log:

docs/attendance-tracking-implementation-plan.md

@@ -0,0 +1,92 @@
+# Attendance Tracking Implementation Plan
+
+## 📋 **Core Requirements:**
+- Real-time event joining system
+- Live attendance tracking during events
+- Speaker material management per event
+- Minimal UI for attendees, informative for admin/speakers
+
+## ⏰ **Event Joining Logic:**
+- **Join Button**: Becomes active exactly when event starts (not 15 mins before)
+- **Join Action**: Marks user as "attended" and "joined" simultaneously
+- **Multiple Joins**: Allowed (user has valid ticket), but attendance count doesn't increase
+- **Attendance Count**: Only increments on first join per user
+
+## 👥 **User Roles & Permissions:**
+
+### **Attendees:**
+- Can join events when they start
+- See basic attendance metrics (e.g., "45 people joined")
+- Access speaker materials only during event
+- Minimal UI design
+
+### **Speakers:**
+- Can join events when they start
+- See complete attendance reports
+- Manage materials in invitation section
+- Cannot change materials once event starts
+- Informative UI design
+
+### **Admins:**
+- See complete attendance reports
+- Real-time attendance dashboard
+- Material management oversight
+- Informative UI design
+
+## 📁 **Material Management:**
+- **Location**: Speaker invitation section (where they receive admin invitations)
+- **Selection**: Speakers choose materials per event via checkboxes
+- **Timing**: Materials locked once event starts
+- **Visibility**: Attendees can access materials during event only
+- **Lifespan**: Materials accessible throughout event duration
+
+## 📊 **Attendance Tracking:**
+- **Real-time Count**: Live updates as users join
+- **Duplicate Prevention**: Multiple joins don't increase count
+- **Status Tracking**: Track both "attended" and "joined" status
+- **Report Data**: Total attendance vs current attendance for mid-event reports
+
+## 🎨 **UI Design Requirements:**
+- **Attendees**: Minimal, clean interface
+- **Speakers/Admins**: Informative, detailed interface
+- **Real-time Updates**: Live attendance counters
+- **Material Access**: Easy access during events
+
+## 🔧 **Technical Implementation Plan:**
+
+### **Phase 1: Database Schema**
+- Add `joinedAt` timestamp to `Booking` model
+- Add `speakerJoinedAt` timestamp to `SpeakerInvitation` model
+- Add `materialsSelected` array to `SpeakerInvitation` model
+- Add `eventStartTime` validation for join button
+
+### **Phase 2: API Endpoints**
+- `POST /events/:eventId/join` - Attendee joins event
+- `POST /events/:eventId/speaker-join` - Speaker joins event
+- `GET /events/:eventId/live-attendance` - Real-time attendance data
+- `PUT /speaker-invitations/:id/materials` - Update material selection
+
+### **Phase 3: Frontend Implementation**
+- Event joining interface with time-based access
+- Live attendance dashboard
+- Speaker material selection in invitation section
+- Real-time updates and minimal UI design
+
+## ⚠️ **Edge Cases to Handle:**
+- User joins multiple times (prevent count increase)
+- Event starts while user is on page (enable join button)
+- Speaker changes materials after event starts (prevent)
+- Materials access timing (only during event)
+- Real-time updates for all user types
+
+## 📈 **Future Report Implementation:**
+- Total attendance vs current attendance
+- Mid-event report generation
+- Historical attendance data
+- Export functionality
+
+---
+
+**Status**: Ready for implementation
+**Created**: $(date)
+**Last Updated**: $(date)

docs/professor-scope-requirements.md

@@ -0,0 +1,122 @@
+# Professor's Scope Requirements
+## Event Management System - Official Project Scope
+
+**Document Version**: 1.0  
+**Created**: January 2024  
+**Source**: Professor's Raw Requirements  
+**Status**: Official Project Scope  
+
+---
+
+## **Official Project Scope**
+
+The Event Management System must implement the following features:
+
+### **1. Event Creation**
+- Admin can create and manage events
+- Event lifecycle management
+- Event status management (Draft, Published, etc.)
+
+### **2. Registration System**
+- Users can register online for events
+- Registration management
+- Waitlist handling when capacity is reached
+
+### **3. Speakers**
+- Speakers can search and get invited to events
+- Speakers can upload slides (presentation materials)
+- Speakers can receive messages from the admin
+- Speaker management and assignment
+
+### **4. Ticketing**
+- Generate and manage digital tickets
+- QR code generation and validation
+- Ticket lifecycle management
+
+### **5. Schedule Management**
+- Manage event timing and sessions
+- Session creation within events
+- Speaker assignment to sessions
+
+### **6. Attendee Tracking**
+- Monitor attendance and check-ins
+- QR code scanning at venue
+- Attendance recording and tracking
+
+### **7. Notifications**
+- Send alerts about upcoming events or changes
+- Email notifications for various events
+- System-generated alerts
+
+### **8. Feedback Collection**
+- Attendees can submit feedback
+- Feedback forms and collection
+- Post-event feedback system
+
+### **9. Reporting**
+- Generate event attendance reports
+- Generate performance reports
+- Basic analytics and reporting
+
+---
+
+## **Scope Boundaries**
+
+### **✅ IN SCOPE**
+- Basic event management
+- User registration and booking
+- Speaker invitation and management
+- Digital ticketing with QR codes
+- Session management within events
+- Basic attendance tracking
+- Email notifications
+- Basic feedback collection
+- Basic reporting
+
+### **❌ OUT OF SCOPE**
+- Multi-track event management
+- Speaker rating systems
+- Advanced material access control
+- Backup speaker management
+- Complex scheduling algorithms
+- Real-time dashboards
+- Advanced communication systems
+- Enterprise-level features
+- Advanced analytics
+- Multi-tenant systems
+
+---
+
+## **Implementation Priority**
+
+Based on the professor's scope, the implementation should focus on:
+
+1. **Core Event Management** (Already implemented)
+2. **Speaker Management System** (Search, invite, messaging, slides)
+3. **Session Management** (Sessions within events)
+4. **Basic Attendance Tracking** (Check-in system)
+5. **Feedback Collection** (Post-event feedback)
+6. **Basic Reporting** (Attendance and performance reports)
+
+---
+
+## **Success Criteria**
+
+The system will be considered complete when:
+
+- [ ] Admins can create and manage events
+- [ ] Users can register for events online
+- [ ] Speakers can be searched and invited to events
+- [ ] Speakers can upload slides and receive admin messages
+- [ ] Digital tickets are generated and managed
+- [ ] Event timing and sessions are managed
+- [ ] Attendance and check-ins are monitored
+- [ ] Notifications are sent for events and changes
+- [ ] Attendees can submit feedback
+- [ ] Basic reports are generated
+
+---
+
+**Document Status**: Official Project Scope  
+**Last Updated**: January 2024  
+**Approved By**: Professor

ems-client/app/dashboard/admin/events/[id]/live/page.tsx

@@ -0,0 +1,12 @@
+'use client';
+
+import { LiveEventAuditorium } from "@/components/events/LiveEventAuditorium";
+import { withAdminAuth } from "@/components/hoc/withAuth";
+
+const AdminLiveAuditoriumPage = () => {
+  return (
+    <LiveEventAuditorium userRole="ADMIN" />
+  );
+};
+
+export default withAdminAuth(AdminLiveAuditoriumPage);