Skip to main content
A Vault browser profile retains encrypted website state so an authorized browser can reuse a login. It can contain cookies, local storage and IndexedDB. Granting access to a profile can grant use of the website account represented by that state.

​
Choose the right kind of state

​
Choose a practical workflow

​
Configure and use a profile

  1. Connect a compatible terminal and workspace.
  2. Open Settings → Vault → Browser profiles with your personal RevoEngine browser session. API keys, service accounts and Support sessions cannot manage these profiles.
  3. Create or select the profile, review its owner and access, and assign the intended terminal/workspace. Profile access does not replace workspace access.
  4. Select the assigned profile in Live Preview, or ask the Assistant to use that authorized profile.
  5. Grant the required network mode in the conversation. Complete login through secure input or private takeover when needed.
  6. After a confirmed save, a fresh compatible browser can restore that website state. Verify the page before performing a consequential action.

​
Sharing and simultaneous conversations

A private profile is restricted by default. The owner can grant explicit users or Groups. Share a profile only when those people should be able to act as its website account. Compatible conversations by the same user can share a live profile context on the same instance, device and workspace. Both need their own lasting approval for the same Local or Full Network mode; one-time or timed grants do not join a shared context. Conversations keep separate tabs and human-control boundaries. Login or logout can change the shared website state. Closing one conversation closes its tabs while other conversations continue. Sharing a profile with another user does not merge different users’ live contexts.

​
Manage the lifecycle

A revision conflict means another change happened after your read. Reload and review current access before saving again. Do not overwrite a changed sharing policy blindly.

​
Recovery and migration

If a page asks for login again, the external service may have expired or revoked its session. Use the human login flow; a saved profile is not a credential-refresh guarantee. Changing network mode can recreate the context. Expect new tabs restored from the last saved profile state, not preservation of unsaved forms. Stopping the runner also ends live contexts. Current runners use Vault profiles. The retired local profile flag is not a configuration option. Legacy snapshots require explicit owner import on a compatible foreground macOS runner; the original is retained by default. That migration restriction does not limit ordinary Vault profile use on supported desktop or service runners. Continue with browser and Live Preview for private takeover, recording, limits and expected outcomes.
Last modified on November 8, 2026