Choose Desktop or Chrome
BrowserSeat Desktop creates isolated browser instances. Public Windows and macOS releases are in development.
The Chrome extension is intended to share a selected tab that is already open. Use this approach for a task within an existing page.
Prepare the shared browser
Open the pages needed for the task and check which accounts are signed in. A guest who can operate a signed-in website may also be able to perform its account actions.
Decide which browser to share and what the guest needs to do. Available permission controls will be documented with each release.
- Use a dedicated browser environment for an ongoing task.
- Keep unrelated accounts and sensitive pages outside the shared space.
- Agree with the guest on the work they are there to do.
Send an invitation
Create an invitation for the browser you want to share. Send the invitation to the guest and approve their connection.
Send access information directly to the intended guest. Confirm who has connected before starting the task.
Keep the host running
The shared browser runs on the host computer and uses its internet connection and storage. Keep the computer powered on, awake, online and running BrowserSeat during the session.
Background hosting uses CPU, memory, bandwidth and storage. The impact depends on the computer, the websites in use and the number of active browsers.
End the session
Review the completed work and end the guest's access. Decide whether downloaded files or signed-in sessions should remain in the browser.
Browser profiles persist on the host. Invitations expire, and the host can revoke guest access. Check release documentation for version-specific limits.