Web access and saved sessions
Public pages need no saved login. Pro users can connect a private web app once, then let a Browser Operator reuse that account within an approved domain boundary without installing an extension.
Connect one website
Open Settings > Web access, paste the HTTPS sign-in address, and complete authentication in the secure browser tab. Return to Settings and choose Finish so the session becomes available to one-click Pro Live Runs.
- Enter the website's HTTPS sign-in page.
- Sign in only to the intended account in the new secure browser tab.
- Choose Finish, then attach a Browser Operator tool with matching approved domains.
Keep the scope narrow
The saved session is account-owned and domain-scoped. A workflow requesting domains outside that scope is blocked before browser execution. Read mode observes; approved-actions mode pauses before consequential interaction and supports human takeover.
Review and revoke access
Settings shows recent Browser Live Run outcomes, attempts, domains, and private evidence. Browser Recipes preserve reviewed goals and scopes for reuse. Remove a recipe independently, or delete the saved website to revoke future browser runs.
- Keep private evidence links inside the intended account.
- Reconnect when the site expires its login.
- Remove the session before changing account ownership.
- Use a native integration instead when it exposes the required typed action.