Atlas connection credentials
Which stored secret each company connection points at, and which connections share one
1 Oct 2026 · branch p3-cred-r2-channel-lifecycle · captured against propflow-stage · at 494a7a2f56d
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · Fairhaven Residential (TEST): the mailbox and calendar share one grant
Both company connections point at the same credential reference, so the block says each shares a grant with the other. Revoking one would take both down. The reference is a pointer to the stored secret, not the secret. Scopes read "not recorded" because nothing stores which permissions were granted.
Asserted in the captured DOM — Connection credentials · mailbox (company) · calendar (company) · ATTACH#mailbox#primary#2026-09-16T04:02:02.904Z · ATTACH#calendar#primary#2026-09-16T04:02:02.942Z · not recorded
Sections 2–2
2 · Negative control: a test company with no hook
A company with no connection says so plainly, and names the next step.
Asserted in the captured DOM — Connection credentials · This company has no live mailbox or calendar hook.
