The same records as the onboarding pages, on their Settings counterparts
9 Oct 2026 · branch feat/settings-last-changed-p6 · captured against propflow-stage · at f34ab7e9f1e+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.
On the stage test company, a temporary application fee is saved for its one building ("Saved" on the card). The header's top right reads Last changed by the person and the time, in the company's time zone. Every answer on this page is an onboarding answer, so the line is the page's own. A page with no recorded change since tracking began shows nothing, as the onboarding pages do (#18250).
Asserted in the captured DOM — Last changed by
The temporary fee is cleared through the same field. Clearing is a change too.
Asserted in the captured DOM — Last changed by
Maintenance also holds settings onboarding never asks, such as the rating texts switch and each building's tech phone, and these records don't cover those. So after a temporary answer to What counts as an emergency? is saved, the line reads Onboarding answers last changed by. It never claims the whole page.
Asserted in the captured DOM — Onboarding answers last changed by
The temporary answer is cleared.
Asserted in the captured DOM — What counts as an emergency?
A new browser session: the building's application fee is empty again, and the line names the newest change, the clear.
Asserted in the captured DOM — Last changed by
And the emergency question reads Not answered yet again.
Asserted in the captured DOM — What counts as an emergency? · Not answered yet.