Share MFA setup securely
Stop sending authenticator QR codes as screenshots in chat. Use an expiring secure share instead.
Open MFA sharing
MFA sharing is currently available from the authenticated dashboard for eligible plans.
Open MFA sharingPublic visitors can read this workflow page; creation stays inside account-controlled product surfaces.
Share MFA setup details securely by using an expiring protected share rather than sending authenticator QR codes or TOTP secrets as screenshots in chat.
What to avoid
- Sending authenticator QR screenshots through chat.
- Saving TOTP seed images in camera rolls or synced folders.
- Leaving MFA setup details in onboarding documents.
Safer workflow
- 1 Use the authenticated MFA sharing workflow when available.
- 2 Limit access to the person taking over setup.
- 3 Set a short expiration and view limit.
- 4 Confirm enrollment and remove obsolete setup material.
Unsafe channel vs safer delivery
Trust Notes
- Built for authenticator setup data
- End-to-end encrypted payload support
- Plan and quota controls
- Expiration and view limits
Common Use Cases
FAQ
Should I send MFA QR screenshots in chat?
No. Screenshots can persist in chat history, backups, and device galleries.
Why is the public page CTA-only?
MFA sharing is a sensitive account-level workflow and stays behind authenticated feature controls.
Can Secret Pusher store TOTP setup details temporarily?
Yes, the product includes an MFA sharing workflow for eligible users.
Related Tools
View all toolsSend an API key securely
Do not paste API keys into Slack, email, or tickets. Create a short-lived encrypted link instead.
Secure file drop
Receive confidential files without asking people to attach them to email or upload them to a permanent shared drive.
Share .env and config secrets securely
Production credentials should not live forever in chat history. Send them through an expiring encrypted link.
Create a one-time secret link
Paste sensitive text, set when it expires, and share a link that burns after it is opened.