About

1. Enter your sign-in nameA request goes to your enrolled devices.
2. Check the digitsYour phone shows the same digits as this screen.
3. ApproveWith your passkey if you added one — and you are in.

Sessions

A fresh random session at every sign-in, kept server-side behind an HttpOnly cookie. 12 hours at most, 1 hour idle.

No data in the browser

Pages render on the server; the admin token never leaves it.

Number matching

A sign-in completes only when the digits on the phone match this screen — and only in the browser that started it.

Least privilege

Every page and action checks your role, re-confirmed with the auth host every minute.

Locked-down pages

A strict content security policy: no inline scripts, no third-party content.

VELVET_AUTH_URL

not set

VELVET_AUTH_PUBLIC_URL

not set

VELVET_AUTH_ADMIN

not set

VELVET_AUTH_APP_KEY

not set

VELVET_SESSION_KEY

not set

Break-glass sign-in

off

Velvet Guard version

0.1.0

Auth host version

not probed yet

VELVET_AUTH_PUBLIC_URL is not set — invite and sign-in links fall back to a local address phones cannot reach.

Values come from the Velvet Guard environment. Secrets are never shown — only whether they are set.

Probed live against the wired auth host. Fleet, members and /trusted soft-derive from /devices on older binaries; IAM write surfaces (roles, apps, permissions, JIT, export, webhooks) stay hidden until the host proves them.

viewer

Overview, fleet and services — read only.

auditor

Reads everything: people, devices, policy and the audit log.

editor

Viewer, plus devices, live sign-ins and liveness checks.

manager

Invites, approves, revokes and offboards people; edits roles, access and apps.

admin

Everything — organizations, permissions, recovery codes and other admins.

Organizations may use their own role names; the permission table gives them meaning.