Complete previous-landlord fields
Enter prior landlord name, email and phone when applicable.
Exact navigationPublic Tenant Application → Previous Landlord
Before you begin
- Use an account with Invited applicant and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Enter prior landlord name, email and phone when applicable. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Public Tenant Application → Previous Landlord.
- Select the exact record or option described in this guide.
- Complete the displayed fields or action using the rules below.
- Save or submit once and resolve any validation response.
- Verify the resulting record, status, file, notification or integration effect.
Fields, choices and supported possibilities
Exact actionComplete previous-landlord fields
Exact navigationPublic Tenant Application → Previous Landlord
Module version1.0.0
Access ruleInvited applicant
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Tenant/applicantIdentity, contact, current address, employment/income, occupants, pets, smoker/benefits/children flags and right-to-rent data where exposed.
Tenancy termsProperty, tenant client, start/end/move-in dates, term, rent, frequency, deposit, holding deposit and deposit scheme.
Consent and workflowInvite mode, consents, review notes, agreement template/body, signature stage and workflow action.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.
Code-backed validations and workflow rules
- Use accurate contact details and obtain/record relevant consent.
- Public application and onboarding actions use token/record checks and explicit workflow states.
- Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
Expected result and verification
- The supported complete previous-landlord fields flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.