S2S Studio
Authentication

Sign into the S2S control plane.

Cookie-backed auth keeps project, review, and voice-consent actions tied to a real operator identity.

Login
Use an Atlas-compatible local account or your configured admin email.

Sessions are stored with cookies and reused across the studio surfaces.

Atlas local default: mir / darkstar1234
Why the sign-in step matters
The app is opinionated about review accountability.

Voice verification, final approval, rejected-line rerenders, and audit log entries all depend on an identified operator session.

The UI keeps those actions close to the work, but the underlying review trail still needs a concrete user for traceability.