What is read-only mailbox ingestion?

A read-only connector copies inbound mail from a mailbox you grant, then you can revoke it. It does not send as the broker, the cedent, or the reinsurer. The marketing site does not take live client packs. Production ingest is tenant-scoped and reversible.

Brokers already live in email. The honest version of "connect your inbox" is OAuth or an equivalent grant into a tenant mailbox, parse attachments, emit a pack, and stop. Write-access to send mail as the user is a different, higher-trust product. Do not buy them as one toggle.

What the grant actually is

Microsoft 365 or Gmail, scoped to one mailbox or one folder, revocable from the same consent screen that created it. The connector copies submissions that arrive. Every read belongs on an audit trail. If security review wants to see the grant, show the grant: read-only, one mailbox, revoke anytime. If they want you to forward packs to a vendor address, that is a different architecture and usually the wrong one.

Read-only does not mean the model may fill gaps because "the email implied the limit." The covering email is a document. If it is the only source, cite it and usually chase the slip. If it conflicts with the slip, it is a conflict. The mailbox is a transport. Provenance is still field to document to page to span. See source-grounded extraction.

Implementation is not a company-wide crawl. Name the inbox whose missed SLA hurts this quarter — submissions, reporting replies, inbound triage — then prove spans on that inbox. Broker operations is the placing view of that grant.

What this website is not

This website is not the tenant. The public pack inspector is a sample so you can see fields, conflicts, and gaps without uploading a real slip. Do not put a live placing file in a marketing form. Create a workspace if you want the sample inside a login. Production files stay where you granted the mailbox.

A chase list still comes out of the same loop. Missing pages and unresolved conflicts are the work queue after ingest, not a reason for the connector to write back to the broker's client. What is a chase list in reinsurance submissions? is that queue. Sending the chase is still a person, unless you have separately accepted a write-access product, which this definition is not.

Worked example: ACME Construction Ltd

Fictional grant: a broker points read-only access at submissions@acme.example. A zip arrives for ACME Construction Ltd. Slip.pdf page 1 names the insured and the period. Slip.pdf page 2 states USD 10,000,000 any one occurrence and TIV USD 42,000,000. SOV.xlsx totals USD 47,100,000. Hours clause is missing.

The connector copies the zip into the tenant. Extraction traces the limit, stores both TIV spans, and puts hours clause on the chase list. It does not email the producing broker as submissions@acme.example. It does not reply to the insured. It does not forward the pack to a market. When the pilot is over, the broker revokes the grant. That is read-only mailbox ingestion.

If a vendor needs you to CC a shared inbox they control, or to paste the zip into a public chat, you are not looking at this grant. You are looking at an export. Copy inbound mail. Do not send as the broker.