Workspace browser data
Understand the workspace extension's browser events, metadata defaults, text collection controls, and rollout requirements.
On this page
The workspace browser extension is a separate enterprise implementation from free Beam Sentinel. It connects a browser profile to a workspace and reports supported browser interactions. Rollout is in progress: the matching dashboard routes and a distributed extension build must be available before employees can use it. This guide describes the implementation, not a completed Chrome Web Store release or verified deployment to your workspace.
Choose the right extension
Free Beam Sentinel checks supported prompts locally, requires no Beam sign-in, and retains a small redacted history in the browser. It does not upload that history to a workspace.
The workspace extension uses device enrollment, membership checks, and an enterprise entitlement. Signing in alone does not enable tracking. Each browser must be explicitly connected, and collection stops when the implementation detects expired policy or lost access. It has a separate device identity from a CLI on your laptop or Raspberry Pi.
Understand the recorded data
| Browser surface | What a record means |
|---|---|
| Supported provider visit | Provider origin, local random session identifier, and timestamp; not whole-browser history |
| Prompt submission | A submission attempt, text length, local decision, and finding categories; not confirmed delivery |
| Composer paste | A paste interaction, length, and findings; not a global clipboard log |
| Attachment selection, paste, or drop | Coarse type and size for supported file paths; file names and bytes are not read |
| Visible response changes | An observed response and its length; a pause in streaming is not proof of completion |
| Copy, regenerate, stop, or share | A supported interface interaction; not proof of the provider's resulting action |
The implementation includes adapters for ChatGPT, Claude, Gemini, Perplexity, Microsoft Copilot, Grok, and DeepSeek. Existing conversations are not backfilled. Provider layout changes can affect capture, and a browser interaction cannot reliably identify whether a human or automation performed it.
Control text collection
Metadata only is the default. Workspace managers can opt into up to 4,000 characters of heuristically redacted prompt, response, or paste text under Policies → Enterprise browser. The extension displays the active collection setting. Known secret patterns are masked, but arbitrary sensitive prose can remain; redaction is not semantic anonymization.
Browser controls use their own provider, attachment, mode, and collection settings. The CLI policy presets configure agent command/tool restrictions; they do not automatically become browser rules. Member overrides cannot enable browser text collection or weaken the workspace browser controls.
Interpret delivery and protection
Browser events use bounded local queues with retry and visible loss accounting. Records may be dropped or expire, so the dashboard is not a lossless transcript. API identity comes from the enrolled device credential, and the server checks membership and entitlement again before accepting records.
Protection operates on supported page interactions. It does not cover arbitrary API calls, native AI apps, every browser network path, or commands that execute on a remote computer. Combine browser records with CLI capture and verify each surface independently during a pilot rollout. Avoid running both extensions in the same profile during that pilot because both can review prompts.