Demo playbook · 3–5 min
Tenant isolation check
Security evaluation: compare demo garage data with owner@other.shop isolation login. Multi-tenant boundary proof.
Role for this script
owner@other.shop
Password is issued on your live demo access desk after you request access (also emailed).
Tenant isolation is mandatory in product design. Local tenant-guard flag may be off in some dev envs — still demonstrate data separation via second tenant.
Request access
Checklist
Step-by-step evaluation
Follow in order. Expected outcomes keep the demo honest.
Step 1 · /dashboard
Login owner@demo.garage — note open job count / customer names.
Expect: Demo garage data
Step 2 · /login
Logout; login owner@other.shop with the password from your access desk.
Expect: Different tenant workspace
Step 3 · Board / customers
Confirm demo-garage ROs and customers are not listed.
Expect: No cross-tenant leak
Honesty caveats
- Never put real customer PII in public demos.
- Production deployments enable stronger tenant-guard and secret-managed credentials.