Gatekeeper rollout part 2c: the Rollout row under each module
The new Rollout select under each module on the admin customer page (Fairhaven Residential (TEST)), and the line the customer's own team reads on a Supervised module's settings page (Sandbox). Stage data source; 20% Collections plans were stored on stage for the capture and ended afterwards.
23 Oct 2026 · branch feat/gatekeeper-rollout-p2c-admin-row-customer-line · captured against propflow-stage · at 9b3a58ac101+local
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 · The Rollout row under each module
Each module now carries a Rollout row, on the same select as Handyman texts. A 20% Collections plan was stored on this test company for the capture, so that row reads 20% send on their own; modules with no plan read Off, every message waits, today's behaviour. A plan acts only while its module is Supervised, and only a system admin can change it.
Asserted in the captured DOM — Rollout · While Supervised, part of the conversations send without waiting. · Handyman texts · 20% send on their own. The new row and its help text sit beside the Handyman texts row it is modelled on; a stored 20% plan reads as 20%.
Sections 2–2 and notes
2 · What the customer's own team reads
Gera's answer to the plan's second question: the customer's team sees the share. With Collections Supervised and a 20% company plan sending, the module's settings page reads Supervised, 20% sending on its own under its header. With no plan, or at 0%, nothing new shows, and customers otherwise still never see the word Supervised.
Asserted in the captured DOM — Supervised, 20% sending on its own. The customer-facing line, with the stored share.
How this was staged
Stage only: one-step 20% Collections plans were stored on Fairhaven Residential (TEST) and Sandbox for the capture and ended right after. Nothing was written to production. The admin page lists only customer companies, so the customer line is shot on Sandbox, where Collections is on and Supervised. The row's load / save / refusal behaviour is also pinned by RolloutRow.dom.test.tsx, and the line's wording and its silence at 0% by rollout-plan.test.ts.