Storage follows the workflow
Signing in establishes an account identity; it does not automatically upload every local profile or make the browser an offline workspace. Local credential storage, an enrolled vault and the hosted cloud workspace have different behavior. They are not four interchangeable choices in a universal settings menu.
| Workflow | What to expect |
|---|---|
| Local workstation | Saves supported profiles and settings on the device. Reusable secrets use the configured vault or operating-system credential store. |
| An already enrolled local vault | Its stored, encrypted data can be unlocked with the required local credentials. Enrollment, account operations and synchronization have separate online requirements. |
| Hosted cloud workspace | Loads and saves protected workspace data through the authenticated cloud service. A successful save requires a service acknowledgment. |
| Temporary connection | Is not a saved inventory or recovery copy. Its availability depends on the deployment's admission policy. |
The hosted workspace needs connectivity
The hosted cloud workspace does not provide a general offline-mode switch. It does not persist a local workspace cache or durable offline write queue. Do not interpret an open page or unsaved changes still visible in memory as an offline backup.
- Sign in to the intended account and unlock the workspace.
- Make a change and wait for its confirmed save state.
- On a failed or uncertain save, use the offered retry or reconciliation controls before making conflicting changes elsewhere.
- Do not close or reload the page assuming that an unconfirmed change is safely retained for later synchronization.
- Lock or sign out when finished on a shared device.
Changing accounts does not transfer ownership of another workspace. A failed cloud write is not permission to save an unprotected local copy.
Local access is not automatic synchronization
An existing enrolled vault's local copy is different from the hosted browser workspace. You need that copy and its unlock material on the device before relying on offline access. Merely signing in on a new device does not reconstruct a locked vault or authorize synchronization.
When reconnecting a supported local vault, review any reported conflict and its verified remote state rather than assuming the newest-looking timestamp must win. Keep a separate backup and recovery plan.
Cloud-only workspace storage does not mean zero local traces. Active memory, browser downloads, screenshots, clipboard history and extensions are separate concerns. See privacy and trust before working on an untrusted or shared device.