Verified Worker-backed demo

Tegy Admin Invite Lifecycle

Evidence for the Claude-like members admin flow: reject Gmail before allowlisting, add gmail.com, invite successfully, and open the invitee onboarding link.

Video Demo

Recorded against the built Tegy UI. API calls were routed into the real Worker collaboration/auth modules with in-memory D1 and a test Email binding, so domain validation, invite creation, link generation, public invite lookup, and onboarding payloads come from backend code.

Reviewed Frames

Contact sheet generated from the final video with ffmpeg and reviewed before shipping.

Contact sheet for admin invite lifecycle demo

Backend Evidence

npm run test:admin-invite passed against real Worker modules and Miniflare D1.
Before allowlisting, marco@gmail.com is rejected with Only emails from @rocketminds.io may be invited.
The rejection payload was checked to ensure it does not mention unrelated stale domains such as msx.dev.
After gmail.com is added through PUT /api/orgs/current/domains, the Gmail invite is accepted and an invite email is sent.
The emailed /join/org/:token link resolves through the public invite endpoint and shows the invited Gmail address in onboarding.
The invited Gmail path resolves to Google sign-in and the simulated Google callback creates an active org membership.

Verification Commands

npm run test:admin-invite
npm run build
npx tsx scripts/run-playwright.ts tests/browser/access-admin.spec.ts
npx tsx scripts/record-admin-invite-lifecycle-demo.ts