Understand customer and contact synchronisation hooks
Know how customer/contact changes support landlord and portal records.
Exact navigationAdmin Area → Customers → open/create customer or contact
Before you begin
- Use an account with Customers capability 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
Know how customer/contact changes support landlord and portal records. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Customers → open/create customer or contact.
- 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 actionUnderstand customer and contact synchronisation hooks
Exact navigationAdmin Area → Customers → open/create customer or contact
Module version1.0.0
Access ruleCustomers capability
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Code-backed validations and workflow rules
- The module registers customer-profile tabs and customer/contact hooks.
- Landlord/customer linking should be verified after changes.
Expected result and verification
- The supported understand customer and contact synchronisation hooks 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.