Understand the internal compliance target list
Know that the model can read compliance_monitor_document_intake targets.
Exact navigationTechnical model capability → get_property_compliance_targets
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 that the model can read compliance_monitor_document_intake targets. 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
User buttonNot exposed in supplied views
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 the internal compliance target list 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.