Passkeys & security keys
Use a supported device or FIDO2 security key. Register a backup before removing your last method.
Account services are being prepared
Individual sign-in and account changes are not available yet. You can explore the account center and security guides.
Security & sign-in
Keep access in your hands.
Passkeys, additional verification and recovery methods belong to your personal account.
Authenticator codes
Authenticator enrollment will require confirmation of a working code before becoming active.
Recovery methods
Recovery codes must be shown once, stored safely and invalidated after use.
Before changing access
Fresh verification, a working alternative and a record of the change will be required. Removing an authentication method will not delete your account.
How do passkeys protect me?
A passkey uses your device or security key to prove you can sign in. Pxster receives a public key, never your fingerprint, face scan or private key. Keep another sign-in or recovery method available before replacing your device.
Learn about passkeys at FIDO Alliance ↗What is two-factor authentication?
Two-factor authentication combines different kinds of evidence. An authenticator app can provide a second factor after a password. A passkey with user verification can provide stronger protection against phishing. Email or social login alone does not automatically satisfy Pxster's security policy.
CISA's guide to MFA ↗What happens if I lose access?
A second credential and single-use recovery codes can help. Never send a password, authenticator secret or recovery code to support. Pxster's recovery process must be available before credential enrollment opens.
Why will sensitive changes ask me to verify again?
Fresh verification helps protect against someone using an unattended or stolen session. Removing a passkey, changing recovery details or deleting an account should require recent authentication.
Do workspace administrators control my credentials?
Workspace policies may require stronger sign-in, but personal credentials and unrelated account activity remain personal. Publishing connections and workspace permissions are managed separately.