Demo Mode

This page documents what administrators see when using the Admin Console in demo mode. Demo mode provides a safe sandbox for exploring administrative features without affecting production data.

What is Admin Demo Mode?

When you switch to the Admin role in a private demo, you enter a restricted version of the Admin Console. Demo admins are identified by their email pattern (@demo.com or @demo.local) and are automatically scoped to their demo tenant's data.

For the full private demo experience (role switching, mock data, demo control bar), see the Private Demo Walkthrough.

Visual Differences

Header

The Admin Console header displays "(Demo)" after "VivaEdu Admin" to clearly indicate you are in demo mode.

Navigation

The side navigation is reduced from 12 pages to 4 pages. Operational and infrastructure pages are hidden.

What You Can Access

Demo admins have access to 4 pages that demonstrate governance and user management features.

Users Page

The Users page shows only users belonging to your demo tenant. Each user displays their demo tenant ID and time until expiry.

Audit Logs

Audit logs are fully functional in demo mode, but scoped to your demo tenant. You can filter, search, and export logs to CSV. All actions you take during the demo (creating vivas, switching roles, viewing student data) are logged and visible here.

For detailed audit logging documentation, see Governance.

What's Hidden in Demo Mode

Eight pages are hidden from demo admins. These pages contain operational or infrastructure-level features that require production access or would not be meaningful with demo data.

Demo Isolation

Each private demo creates an isolated "bubble" with its own unique tenant ID. This ensures complete data isolation between demos.

• Unique tenant ID: Each demo is assigned a unique demoTenantId (for example, demo_a1b2c3d4).
• Data scoping: All data created during the demo (users, classes, vivas, audit logs) is tagged with this tenant ID.
• Query filtering: Database queries automatically filter by tenant ID, so demo admins only see their own data.
• No cross-contamination: Multiple concurrent demos cannot see each other's data.

What Gets Scoped

• User accounts (teacher, student, TA, admin)
• Classes and enrollments
• Assignments and viva sessions
• Student responses and recordings
• Audit log entries
• LTI context records (if any)

Demo Data Lifecycle

2-Hour Timer

Each demo session lasts 2 hours from creation. A countdown timer is displayed in the demo control bar. When the timer reaches zero:

1. You are automatically logged out
2. The demo cleanup worker marks your tenant for deletion
3. All demo data is permanently deleted within 15 minutes

Automatic Cleanup Process

The demo cleanup worker runs every 15 minutes and deletes expired demo data in a specific order to respect database foreign key constraints:

Key Points