Real Estate Management module overview
This guide explains the connected staff, client, broker, landlord, supplier and public workflows. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Property Operations → Dashboard
Before you start
- Use an account with real_dashboard: View 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 you’ll accomplish
Understand the connected staff, client, broker, landlord, supplier and public workflows. 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 → Property Operations → Dashboard.
- 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.
- Check the resulting record, status, file, notification or integration effect.
Fields and options to review
Exact actionReal Estate Management module overview
Exact navigationAdmin Area → Property Operations → Dashboard
Module version1.0.0
Access rulereal_dashboard: View
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Rules the system enforces
- Module version is 1.0.0 and the header requires CRM 2.3.*.
- The module extends CRM customers, staff, roles, items, contracts, invoices, payments, tasks and portal hooks.
How to confirm it worked
- The supported real estate management module overview 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.
Continue with related guidance
Connected discovery, service and API guides
Was this guide useful?Your response is stored only in this browser.