Whose website session is used?
The remote browser is associated with an account and authenticated user. That user’s AI Employees can share the browser context. It is not a separate set of website logins for every worker.- Another member does not receive your browser merely because they can use the same worker.
- A run without the required account and user identity does not receive your private browser through the remote browser command boundary.
- A worker’s manager assignment is not a transfer of another person’s website sessions.
- Conversation sharing and browser-session ownership are separate controls.
Choose a restricted website identity
Before signing in:- Check the active Odella account and signed-in member.
- Use a website account approved for the task, with only the provider-side permissions it needs.
- Avoid signing a broad administrator account into the worker’s browser for a narrow lookup task.
- Review which of your workers you will ask to browse. A shared user context does not establish per-worker website isolation.
- Use an authorized connected API with explicit action controls instead when the task requires a boundary that browser work does not provide.
Saved logins and saved sign-ins are different
Browser sign-in state is protected through Vault but is not listed as an editable login or key, nor offered as a credential item to workers. Authorized browser services restore it for supported use; this is not a zero-knowledge password manager.
Saved browser state expires after 30 days without use. Providers can expire their own sessions sooner. Do not rely on inactivity expiry as an immediate revocation procedure.
Sign out and revoke deliberately
Open Account → Vault, find Browser sign-ins, and select Sign out of all sites. Review the confirmation. This closes your active browser context and deletes the saved sign-in state for the current account and user. After signing out:- Return to Vault and confirm sign-ins are no longer shown as saved.
- Open a safe test website through supported browser work and confirm it no longer resumes the old authenticated session.
- If the provider may still have active sessions or credentials, revoke them using the provider’s administration controls.
- Separately remove obsolete login items, API-key grants, and integration connections as required.
Signing out does not undo website changes, delete files already downloaded, or
recall information already returned to a conversation. For a suspected
exposure, stop the affected work and follow your organization’s incident
process; contact Odella at support@odella.ai.
Downloads and browser outputs
A private browser session does not make every result private forever. A downloaded file handed to a worker, an extracted page summary, or information placed in a conversation becomes an output that needs its own audience and retention review.- Use non-sensitive sample downloads during onboarding.
- Review the destination workspace, conversation, document store, or workflow that receives the output.
- Check access to that destination separately from website-login ownership.
- Do not assume signing out deletes earlier outputs or blocks their later use.
- Do not put cookies, session data, passwords, or authentication headers into chat, instructions, skills, or shared files.
Test a signed-in workflow safely
If a test reveals unexpected access, stop the workflow and review user identity, website permissions, saved sign-ins, output audiences, and the control boundary used. Do not simply broaden permissions to make the test pass.
Read Tool and browser boundaries for execution safeguards, Vault for credential controls, and Security review checklist for evidence to collect before production use.

