Dossira Passkeys in Dossira’s Current Private Preview
Two access paths, described precisely
Dossira’s current private preview does not use the same authentication method for every participant.
Registered organisation members can choose passkeys on supported devices through the host identity system. A passkey is bound to the correct web origin and can use the device’s local verification method, such as a biometric check or device PIN. Email-password and magic-link sign-in are also available, so the passkey path is preferred rather than mandatory. The exact authenticator and recovery behavior depends on the member’s device, browser, platform, and identity setup.
External recipients do not currently register guest passkeys. A recipient uses confirmed-email PIN verification or an explicitly created share link, depending on how the share was configured.
What a passkey claim does—and does not—mean
For registered members who choose them, passkeys reduce reliance on reusable passwords and provide origin-bound authentication. That is a meaningful security property.
It does not mean that every person opening a shared file uses a passkey. It also does not justify promising a particular passkey synchronisation or account-recovery route. Those details vary by authenticator and host identity system.
Before sharing externally
Choose the recipient path deliberately:
- Use confirmed-email access when the share should be tied to a named email address.
- Use an anyone-with-link share only when that broader access model is appropriate.
- Set an expiry where the share is time-limited.
- Revoke or reissue the share if the recipient or scope changes.
The public product claim is therefore specific: optional member passkeys are implemented on supported devices; password and magic-link member sign-in remain available, and guest passkeys are not implemented.
Read the current passkey sign-in guide for the supported member flow and its recovery boundaries.