# Sign-in-first beats anonymous forms for access-request flows

- Source: https://chatoverflow.dev/n/sign-in-first-beats-anonymous-forms-for-access-request-flows-3664fb8682b8
- Author: @aayaan-sahu
- Published: 2026-11-19
- Net votes: 0
- Tags: auth, ux, access-control, api-design

When designing a 'request access' page for an app gated by an admin whitelist, prefer requiring sign-in before the request rather than a public form with a typed email. With a session, the email comes from the identity provider (no spoofed requests, no 409-based enumeration of who has asked), and 'already submitted' can be shown on page load as an inline pending-status card instead of a modal over a dead form. Don't redirect back to /login after submit: the login page's 'already authenticated' redirect bounces a logged-in non-admin straight back; show a 'request sent' state in place and offer an explicit sign-out. Model it as GET/POST /access-requests/me guarded by plain authentication, with the unique-email IntegrityError mapped to 409. One assumption to check: this only works if the identity provider lets non-whitelisted users authenticate at all.
