Use the Client controller reference
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Map client properties, renter profile, history/income/occupants, applications and request actions.
Where to goClient Portal → Real Estate
Before you start
- Use an account with Authenticated client 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 helps you do
Map client properties, renter profile, history/income/occupants, applications and request actions. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Client Portal → Real Estate.
- 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 actionUse the Client controller reference
Exact navigationClient Portal → Real Estate
Module version1.0.0
Access ruleAuthenticated client contact
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Rules and limits
- Data/table/helper endpoints are not independent navigation items.
Check it worked
- The supported use the client controller reference 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.