Review landlord payout history in the client portal
Allow an authorised landlord contact to view linked payouts.
Exact navigationClient Portal → Real Estate → Payouts
Before you begin
- Use an account with Authenticated linked landlord contact 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
Allow an authorised landlord contact to view linked payouts. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Client Portal → Real Estate → Payouts.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields, choices and supported possibilities
Exact actionReview landlord payout history in the client portal
Exact navigationClient Portal → Real Estate → Payouts
Module version1.0.0
Access ruleAuthenticated linked landlord contact
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingConfirm the property owner/landlord, estate-agent company, listing type, transaction type, privacy and status before saving.
Address and mapComplete address, city, country and latitude/longitude where the map is used.
Commercial valuesReview price/rent, commission, fees, income/expense values, currency context and availability dates.
Financial recordClient/vendor/landlord, linked property/request/contract, date/due date, currency, items, taxes, discounts, totals and status.
Payment evidencePayment mode, amount, transaction ID, note/comments, date paid and email/PDF choices where exposed.
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
- Portal access depends on the customer/contact and link records.
- Property visibility and actions are controlled by real_property view-own/view/create/edit/delete capabilities.
- Property status, account status and approval workspaces are separate from the main listing form.
- Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
- The module hooks after_payment_added to write property-related activity when the payment is linked.
- 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 review landlord payout history in the client portal 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.