Why Does MailOnce Require Approval After Scanning the QR Code?
Understand why a scan starts a request but the existing session still controls permission.
Why approval matters
Approval prevents a person who merely sees or scans the QR code from silently entering the inbox. The existing session remains in control.
A scan proves proximity, not ownership
Someone can photograph a screen or scan a code without being the person who owns the active inbox. Requiring confirmation turns that weak signal into a deliberate access decision.
Device linking keeps the task inside one active MailOnce inbox. The QR code is only a short request mechanism; access still depends on approval from the browser that already controls the inbox.
Approval fixes the weak part of a QR scan
A scan can show that a device was close enough to see the code, but it cannot prove that the device belongs to the person controlling the inbox. The approval step adds the missing decision: the current session must recognize the request and choose to let it in.
The practical takeaway
Approval exists because seeing a QR code is not enough evidence to trust a new device.
Try MailOnce
Move one active inbox between your own devices
Create a temporary inbox, then link another device only when your task genuinely moves from one screen to another.
Create temporary emailRelated device linking guides
Continue with the device-linking topics closest to what you just read.
How to Open the Same Temporary Inbox on Another Device
Continue with the inbox already receiving your messages instead of creating a second address.
Read guideHow QR Device Linking Works in MailOnce
Follow the request from rotating QR code to browser approval and access on the second device.
Read guideIs QR Device Linking Safe?
See the security boundary of short-lived QR requests, explicit approval and recognized devices.
Read guide