Return path
Fast sign-in first. Invite recovery remains available when needed.
Login exists to recover the same workspace, not to create a second account or reset the founder journey.
Returning founders should see the fastest supported path first, with fallback recovery visible when it preserves the same workspace.
Founder access
Provisioned founders use the fastest available sign-in path. Invite-token access stays visible for recovery and reviewed access.
Firebase sign-in
Firebase is the fastest return path for provisioned founders. Invite-token recovery still remains available when a deliberate fallback is needed.
Founder recovery
Use the sign-in or invite-token path already tied to the founder email. Returning founders should never need to restart onboarding to recover a workspace.
Firebase is the fastest return path for provisioned founders in this environment, but recovery still preserves a deliberate fallback.
Recovery model
Login is not a detached support page. It should explain the supported path, the fallback, and what the founder should do next if the workspace already exists.
Recovery principle
Founder recovery should not feel like a hidden support flow. Login stays linked to pricing, signup, and waitlist so the path remains coherent.
Recovery principle
Invite-token access remains a first-class recovery option whenever the faster identity path is incomplete, staged, or simply not the right fit for this founder.
Recovery principle
The recovery path should reinforce that founder access is workspace-aware and identity-bound, not a detached marketing login.
FAQ
A polished login page explains the supported access path while still giving provisioned founders a fast path back into the workspace.
Use the path the product presents. Fast sign-in is the shortest return path, while invite-based access remains valid for reviewed recovery.
Founder recovery
The login surface should make the supported path obvious while preserving a safe fallback whenever direct access is not the right path.