Before you begin
Name the customer-owned source or destination and obtain its administrator’s permission. Use an approved nonproduction mailbox, drive location or collector with synthetic content.
- Agree the connector’s exact read/write scope and any external consent.
- Check the integration’s proof label before changing production routing.
Supported scope and current status
Fetches and transiently inspects document bytes already sitting in configured drives, then reports findings without retaining source content in evidence or durable content storage. Checks the whole message, including attachments, and decides before it is accepted for delivery. There is nothing to recall afterwards. Delivery connectors export content-free decision references, not source documents.
- Choose the matching /integrations page and /coverage tier.
- Separate discovery, remediation and delivery as distinct actions.
Compare this path with the published coverage table and the coverage guide.
Set up the path
Have the service administrator grant the least scope needed for the selected connector and agree the test population. RedactWall assists with the product-side connection; customer consent and source-system policy changes remain customer decisions.
- Confirm the exact drive, mailbox, next hop or recipient.
- Save and read back the approved scope before a scan or mail-flow change.
Use the workflow
Run one bounded synthetic source test. For drive discovery, inspect a known file and read the finding; for mail, send an allowed and denied test; for event delivery, watch the chosen recipient.
- Record the exact selected population.
- Avoid using a real customer document to establish first value.
Verify the result
Verify a drive finding against the selected source, a mail refusal against zero next-hop delivery, or a delivery reference against the receiving system. An empty result with a failed connector is not a clean scan.
- Read back connector health and any truncation or unreadable status.
- Confirm a blocked mail test did not reach the next hop.
Coverage references: 11 requirements, 0 currently passed
This guide is bound to 11 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
Missing permissions, stale source revisions or an unavailable downstream recipient require explicit repair. Stop the operation rather than widen access or treat a retry as a second approved action.
- Ask the source administrator to correct the scoped grant.
- Re-run the same synthetic test after a fresh readback.
For customer-side next steps, read Recovery and support.
Billing and integration handoffs
Connector permissions belong to the customer’s Microsoft, Google, mail or destination account. These broader paths are outside the proposed first pilot unless separately scoped and verified; provider charges may be separate.
- Confirm connector and integration availability for your agreement.
- Coordinate any device-seat impact separately.
Limits to keep in view
The current public site labels Microsoft 365 and Google Drive as built and tested to their connections, email as tested against a real cluster, and all as outside the proposed first browser pilot. These labels do not prove a current live customer integration.
- Do not describe discovery as automatic quarantine.
- Do not infer universal mail or cloud coverage from a named connector.
Review the current Disclosures before relying on a capability.