Case study
Designed the central authentication experience used by every Securibox product — creating a single, consistent identity layer across the ecosystem.
Outcomes
Context
Every Securibox product required authentication. Without a central identity layer, users faced repeated sign-ups and inconsistent flows across the ecosystem, eroding trust.
The identity question:
How do we make authentication feel like a trusted entry point to a unified platform, not a gate at every individual product?
Process
Phase 1
Flows
Identity UX design
Designed OAuth flows (Google, Microsoft) and registration flows for cross-product consistency.
Phase 2
Accessibility
RGPD-compliant auth
Ensured auth forms and flows met RGPD standards — critical for enterprise clients.
Implementation
Design
What was designed
- —OAuth (Google, Microsoft) and email registration paths as one consistent first step into the Securibox ecosystem.
- —Registration and recovery framed so authentication feels like a welcome entry, not a separate gate per product.
- —RGPD-aligned copy and consent patterns suited to enterprise expectations.
Code
What was built
- —Production UI in React (Vite): OAuth redirects, email/password sign-up and sign-in, recovery, and cross-product return URLs with client-side validation aligned to server expectations.
- —Controlled forms, explicit error surfaces, and WCAG-oriented focus order for predictable outcomes in review.
- —One shared shell so dependent products inherit the same keyboard behaviour, error patterns, and trust cues.
Trade-offs & Learnings
Auth is often treated as an afterthought. Making it central to the design language ensured every product inherited the same trust baseline.
One identity across the entire platform.
Auth that feels like a welcome, not a checkpoint.