Before you begin
For the proposed pilot use an enrolled Chrome profile on managed Windows 11, a signed-in standard ChatGPT composer and an approved policy. Obtain the organization’s device and browser management consent.
- Use only synthetic test strings.
- Confirm the extension assignment and policy owner before opening the test page.
Supported scope and current status
The proposed first pilot scope is: Typed or pasted text in the standard signed-in ChatGPT composer, in an enrolled browser profile. The extension does not proxy all page traffic, and the existing site does not claim files, images, voice, responses, other ChatGPT modes, Edge or unmanaged browsers.
- Check /coverage for the device tier.
- Read /faq#disclosures for the dated proof boundary.
Compare this path with the published coverage table and the coverage guide.
Set up the path
The browser administrator installs the approved extension in the managed profile and confirms the enrolled device and policy. A mere extension icon does not establish active interception.
- Check the exact supported origin and editor on one test profile.
- Read back policy activation separately from package installation.
Use the workflow
Submit an allowed synthetic message, then a synthetic sensitive value in the same supported composer. Observe the browser action without including a real secret or customer record.
- Capture whether the action was allowed, transformed or refused.
- Test another mode separately rather than assuming it shares this interception.
Verify the result
Compare the browser decision with the actual submitted text and a matching content-free event. Managed installation and composer interception still need a current managed-endpoint run before enrollment.
- Verify allowed and refused outcomes independently.
- Confirm the event names the correct policy and device without exposing prompt contents.
Coverage references: 9 requirements, 0 currently passed
This guide is bound to 9 requirements in RedactWall's acceptance crosswalk, which is maintained internally and not published. A requirement counts as passed here only after current evidence for every bound scenario and authority has been published; none has been published yet.
See the public verification overview and the documentation coverage guide.
Denials and recovery
If the extension is absent, policy is stale or the editor is unrecognized, treat the path as uncovered and stop the pilot test. Restore the known managed configuration before retrying.
- Ask the browser administrator to confirm assignment and policy adoption.
- Re-run the exact synthetic action after a fresh status read.
For customer-side next steps, read Recovery and support.
Billing and integration handoffs
A browser sensor on an admitted managed machine shares that machine’s device seat with an endpoint agent. Browser coverage does not imply that separately routed gateway traffic is enabled.
- Check seat admission on /pricing before cohort rollout.
- Coordinate a gateway application as a separate integration and proof path.
Limits to keep in view
Managed installation and ChatGPT composer interception have not yet been run on a managed Windows 11 endpoint. Dated proof is published before enrollment. Current proof and supported browser versions must be checked before customer enrollment.
- Do not describe this as universal browser or response protection.
- Keep bypass routes and unsupported modes visible in the test report.
Review the current Disclosures before relying on a capability.