Add Live View to your application
Authorize the viewer through your backend before exposing a session-scoped connection.
The connection API can issue a Live View URL. TabSail does not currently provide a separately versioned React embed component or a qualified cross-origin embedding SDK.
Backend flow
- Authenticate the person using your application.
- Load the person's task and its session ID from your own database.
- Check that the person may view that session.
- Request a view grant using the project key held by your backend.
- Deliver the grant URL over an authenticated response and open it for the authorized person.
Do not accept an arbitrary session ID from the browser and forward it with an unrestricted project key. Follow the multi-user authorization pattern.
Embedded viewers
If you display the viewer in a frame, qualify your own origin, CSP, frame policy, browser permissions, mobile interaction, and reconnect behavior against the deployed instance. A URL that opens in a new tab does not prove that every embedded environment is supported.
Keep a direct-view fallback and an explicit expired/ended-session state. Avoid placing grant URLs in analytics events, error trackers, browser history shared with other users, or untrusted referrers.
Human control
Viewing and controlling require separate authorization in your application. A control grant includes a handoff ID and is valid only for the corresponding human-control epoch. Show a clear return-to-automation action; leaving the page is not a completed handoff.
See Human handoff for the control lifecycle and reconnect requirements.