Mission identity & governed cloud access

Sign in. Select a mission. Keep provenance intact.

Authentication never unlocks cloud writes by itself. Synchronization requires an active mission membership, and live physiological capture uses a crew-self mission context only when that membership identifies the crew member.

First mission activation

For a brand-new deployment only: an authorized administrator must provision the first mission operator before invitations can be issued. Existing deployments do not require this step. Creating an account alone does not grant mission access.

  1. Create and confirm the intended operator account using the form below.
  2. Have an authorized deployment administrator run the existing one-time server-side bootstrap procedure documented in SECURE_BOOTSTRAP_AUTH_READINESS.md. Never paste privileged keys or passwords into this page or a chat.
  3. Sign in again, then use Mission & Crew Operations to create active crew members and issue one-time crew-self and ground-medical invites.
  4. Have each invited person sign in with their own account and accept their invite here. Only then perform synthetic browser-to-cloud validation.

No automatic user, mission or membership creation occurs on this page.

Mission access

Mission sign-in

Enter your existing password. New-password requirements apply only when creating or changing a password.

Security boundary

Signing in establishes identity only. Mission tables remain protected by RLS and mission membership.

New accounts have no mission access until an authorized operator issues an invite or provisions membership.

Local encrypted capture keeps working while signed out; cloud synchronization stays locked.