Mobile Hand-off Workflow

This flow leverages Context-Aware Deep Linking combined with Short-Lived Authorization Tokens. Architecturally, this moves the "Capture" workload from the managed workstation to a personal device (BYOD context), reducing friction. The critical security pattern here is that the QR code encodes a One-Time Token (OTT) rather than just the Order ID, preventing unauthorized uploads if the QR code is intercepted or photographed.

Here is the sequence diagram for the Mobile Hand-off Workflow.

Architectural Nuances

• Decoupled Channels: The Desktop and Mobile act as two independent clients. They don't communicate directly (P2P); they communicate through the shared state in the Server.
• Token Scoping: The accessToken generated in Step 2 should be scoped specifically to write permissions for that specific Order ID, not a general session login. This ensures that if the QR code is shared, the worst that can happen is someone uploads a file to that specific order, not accessing the whole system.
• State Synchronization: In Step 14, the Desktop needs to know the upload is finished. This is best achieved via WebSockets (Server-Sent Events) for a "real-time" feel, or simple short-polling if WebSockets are not feasible in your network stack.