Understand compatible property-table detection
Know which table names the module checks.
Exact navigationAdmin Area → Licence Applications → New/Edit Application
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide covers
Know which table names the module checks. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the case or technical integration area described.
- Confirm the linked property and compatible module/table exist.
- Use only exposed UI actions; treat model-only methods as unexposed capabilities.
- Verify any resulting record against the source property and document.
Fields, choices and supported possibilities
Candidatesreal_properties, real_property, realestate_properties, properties
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-property-compliance/
Code-backed validations and workflow rules
- The supplied module contains the stated integration helper or hook.
- No user workflow should be invented where the controller/view does not call the model method.
Expected result and verification
- Understand compatible property-table detection completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.