Atlas granted scopes
Connections record the scopes the provider granted; older ones say not recorded
2 Oct 2026 · branch p3-cred-r2-granted-scopes · captured against propflow-stage · at 9f2805d62e5
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): connected before this change, so scopes read not recorded
Both company connections were made before connects started recording scopes. Nothing backfills them, so the scopes column reads not recorded. It never shows the scopes we ask for, because a consent can grant less. A connection made after this change shows the list the provider returned. That rendering is pinned by tests, because making a real consent on stage is a provider sign-in a person has to do.
Masked for publishing: 7 × property-line, 1 × tester — PropFlow's own lines, as listed in config/phone-registry.json. Any other phone number on the page was left in place for the contact scan.
Asserted in the captured DOM — Connection credentials · not recorded · shares a grant with calendar
