Get started with a guided pilot

Before you begin

Choose a policy owner and an administrator for the managed Windows 11 and Chrome cohort. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment.

1. Write down the ChatGPT text workflow to test and any separately routed Anthropic application.
2. Keep customer records, credentials and prompt content out of an initial support inquiry.

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. An application explicitly routed through the Anthropic gateway is a separate path with its own verification. Managed-device proof is not yet published as current.

1. Compare the proposed scope with /coverage and /faq#disclosures.
2. Treat files, images, voice, responses, Edge, BYOD and other apps as outside this first pilot.

Compare this path with the published coverage table and the coverage guide.

Set up the path

Ask RedactWall about the status of the pilot terms and use only the offered request entry on /get-started. Request initiation, identity verification and approval are separate states; confirm the live sequence for your release before starting.

1. Wait for employee approval and the owner email before attempting workspace access.
2. Have your organization approve the policy, reviewer roles and device-management handoff before enrollment.

Use the workflow

Start with one managed device and synthetic text. Use the approved policy on the enrolled browser profile, then consider a small cohort only after the first path has a verified result and rollback.

1. Check extension installation, device admission and policy activation as separate states.
2. Run the agreed safe submission and record the destination outcome.

Verify the result

Compare the observed destination bytes or refusal with the corresponding decision and evidence. A request, a sign-in and a declared scope are not proof of protection.

1. Read the actual device and policy status after the test.
2. Verify the Anthropic gateway independently if it is in the agreement.

See the public verification overview and the documentation coverage guide.

Denials and recovery

If the workspace is unavailable, ask whether the request was approved; sign-in alone does not create a tenant. If the sensor, policy or evidence readback is unavailable, pause expansion.

1. Keep the last known safe policy and contact support with time, device reference and non-sensitive error details.
2. Repeat the synthetic test only after the condition is resolved and a fresh result can be read.

For customer-side next steps, read Recovery and support.

Billing and integration handoffs

The guided pilot is free within its published time and managed-device bounds. Conversion is requested in the console and a RedactWall employee confirms seats and terms before billing; invoice is the default path.

1. Confirm who manages Chrome and the device before the enrollment handoff.
2. Review /pricing for the current seat rule and configured card-payment limit.

Limits to keep in view

The proposed pilot is not a statement of current release readiness. The published Anthropic live-service proof is dated August 14, 2026. It does not establish current release readiness or browser coverage. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment.

1. Do not enroll a customer device until the terms and release evidence are accepted.
2. Use /privacy and /faq#disclosures for handling and proof limits.

Review the current Disclosures before relying on a capability.