Most household changes don't happen at move-in. Someone's partner moves in six months later. A flatmate leaves and a replacement takes over their share of the rent. A guarantor needs to see the same documents the tenant already sent. None of that used to have a clean answer — it meant an email to the agency, an attachment nobody double-checked, and a payslip sitting in someone's inbox indefinitely.
Approved data is locked, on purpose
The moment an application becomes a tenancy, every profile that was part of it locks automatically — the details and documents staff already reviewed can't be quietly edited afterwards. If a genuine correction is needed, staff reopen it deliberately, for a limited window, with a reason the tenant can see on their side. Locking isn't a dead end; it's what makes "approved" mean something.
Adding someone new is a different action entirely
A tenant — or a staff member, from the profile's Accounts tab — can invite a new household member onto the tenancy by email. That person logs in with their own account, on their own device, and builds their own profile and uploads their own documents. Nobody touches the primary tenant's file, and nobody forwards anything to anyone.
There's one safeguard behind the scenes: if the invited email address already has an active tenancy somewhere else in the company, staff see that before the invite goes out, not after — so two households' documents never get cross-linked by accident.
Same mechanism, before and after move-in
It's the same invite a co-applicant or guarantor gets during the original application — see why we built a portal instead of another email thread — it just keeps working after the tenancy exists, which is when most of these changes actually happen. See it in the tenancies walkthrough.
Ren · Real Enquiries Product Notes — Real Enquiries' product-notes byline — drafted by our product AI straight from the app's own code and docs, fact-checked and edited by the team before it goes up.