Demo Mode

VivaEdu's private demo system creates isolated testing environments for exploring features, training staff, and demonstrating the platform.

What is Demo Mode?

Demo mode creates a completely isolated "bubble":

• Duration: 2 hours per demo session
• Isolation: No access to real production data
• Mock data: Pre-populated with sample users, classes, and vivas
• Role switching: Switch between teacher, student, TA, admin instantly
• Auto-cleanup: All demo data deleted after 2 hours
• Unlimited demos: Start new demos as many times as needed

Starting a Demo

From Landing Page

1. Visit VivaEdu landing page
2. Click "Start Private Demo" or "Free Demo"
3. Demo introduction page appears
4. Click "Start Demo"
5. Demo environment created:
   • Unique demo tenant ID
   • Teacher, student, TA, admin accounts
   • Mock classes with mock students
   • Sample vivas with mock responses
6. You're logged in as teacher by default

As Administrator

Administrators can start demos for:

• Testing new features
• Training new instructors
• Demonstrating to institutional stakeholders
• Verifying audit logging
• Creating training materials

Demo Features

Role Switching

1. Look for demo control bar (bottom of screen)
2. Click role dropdown
3. Select: Teacher, Student, TA, or Admin
4. Page refreshes with new role
5. Experience different perspectives instantly
6. All data persists across role switches

Mock Data

Demo environments include:

• Mock students: Pre-populated student accounts
• Sample classes: Classes with enrolled mock students
• Pre-created vivas: Vivas in various states
• Mock submissions: Sample viva responses with:
  • Synthesized audio (Azure text-to-speech)
  • Generated transcripts
  • Various completion states

Demo Timer

• Countdown timer shows remaining time
• Displayed in demo control bar
• Warning when time is running low
• Auto-logout when timer reaches zero
• All data deleted automatically

Admin in Demo Mode

Audit Logs

• Switch to Admin role in demo
• Access audit logs
• See logs scoped to your demo tenant
• All actions within demo are logged
• Test audit functionality safely
• Verify what gets logged

Use Cases for Admin Testing

• Verify audit logging captures important actions
• Test data export functionality
• Understand what administrators see
• Practice using filters and search
• Test CSV export of logs

Demo Limitations

Demos are comprehensive but have intentional limitations:

• No real LMS: LMS features simulated
• Mock audio only: Viva responses use TTS, not real recordings
• No external emails: Notifications logged but not sent
• 2-hour limit: Cannot be extended
• Limited mock students: Typically 5-10 mock students
• Simplified features: Some advanced features may be simplified

Demo Data Cleanup

What Happens at Expiry

When 2 hours elapse:

1. User is automatically logged out
2. Demo cleanup worker is triggered
3. All demo data deleted:
   • Demo users (teacher, students, TA, admin)
   • Demo classes and enrollments
   • Demo assignments and vivas
   • Mock viva responses and recordings
   • Demo audit logs
4. Storage files deleted (videos, audio, images)
5. Database records purged
6. Demo tenant ID marked as deleted

Cleanup Verification

• Cleanup is logged in production audit logs (system actor)
• Shows demo tenant ID and deletion stats
• Administrators can verify cleanup occurred
• No orphaned data remains

Best Practices