Troubleshoot a missing landlord property
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Check owner/customer link, property owner fields, active status and portal contact.
Where to goAdmin Area → Customers → landlord → Linked Properties
Before you start
- Use an account with Customers/Property access 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 helps you do
Check owner/customer link, property owner fields, active status and portal contact. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Customers → landlord → Linked Properties.
- 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 and options
Exact actionTroubleshoot a missing landlord property
Exact navigationAdmin Area → Customers → landlord → Linked Properties
Module version1.0.0
Access ruleCustomers/Property access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingVerify 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 valuesCheck price/rent, commission, fees, income/expense values, currency context and availability dates.
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.
Rules and limits
- A property can exist without the client-link row needed for portal display.
- 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.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
Check it worked
- The supported troubleshoot a missing landlord property 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.
Related guides
Was this guide useful?Your response is stored only in this browser.
