Company › Notifications and Company › Go-live — their own pages
sr-company-topics part 2. Captured as a customer company admin on stage.
24 Sept 2026 · branch settings/sr-company-topics-p2-notifications-golive · captured against propflow-stage · at 6cfced1db3+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 · /settings/notifications — one switch, and the page names itself once
“Notifications” is the h1 and the crumb. The card underneath no longer repeats that word as its own heading.
Asserted in the captured DOM — Notifications · Share staff notices with PropFlow. The page title and the switch are both on screen for a company admin.
2 · /settings/go-live — refused, and it says so
For this identity the checklist route answers 403, and the page says so instead of going blank. The identity is the only non-staff evidence account, and /api/auth/me reports it as org_admin, but the checklist route's own role read refuses it. Staff are refused by design (no home company). So no account available to this tool can photograph the populated checklist or the /settings banner, and both are pinned by PreLaunchChecklistCard.states.test.tsx and go-live-banner.test.tsx.
Asserted in the captured DOM — Go-live · This checklist is for your company's own admin.. The refused state renders as a sentence, not a blank page.
3 · /settings — both topics linked; the banner stays silent for a reader the checklist refuses
Neither card is on the Company page any more, and the link card lists Notifications, Team and Go-live. The “N items left before launch” line reads the same route as the checklist, so for this identity (refused, as above) it correctly renders nothing: the absence is the 403 path, not a missing banner. Its visible states are pinned in go-live-banner.test.tsx.
Asserted in the captured DOM — More company settings · Choose whether the notices Clara sends your team also go to PropFlow. · What is left to do before PropFlow turns Clara on for your company.. All three topic links render on the Company page.
