Understand compliance target key format
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Identify the internal intake target passed to synchronisation.
Where to goTechnical model capability
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify 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 helps you do
Identify the internal intake target passed to synchronisation. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the case or technical integration area described.
- Verify the linked property and compatible module/table exist.
- Use only exposed UI actions; treat model-only methods as unexposed capabilities.
- Check any resulting record against the source property and document.
Fields and options
Target keycm_intake:{id}
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-property-compliance/
Rules and limits
- 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.
Check it worked
- Understand compliance target key format 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.
Related guides
Was this guide useful?Your response is stored only in this browser.