Understand the unexposed compliance-sync limitation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/licence-applications-understand-the-unexposed-compliance-sync-limitation Publisher: Pixie Technologies LLC Property and Compliance Monitor integration Understand the unexposed compliance-sync limitation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Do not expect a staff button or controller route to call the model sync method. Audience: CRM staff; Permission: Edit Licence Applications / technical administrator; Module v1.0.0; Where to goAdmin Area → Licence Applications → Case 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 Do not expect a staff button or controller route to call the model sync method. 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 Supplied UI actionNone 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 the unexposed compliance-sync limitation 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 Understand dynamic compliance column mapping (https://pixiecrm.com/help-centre/licence-applications-understand-dynamic-compliance-column-mapping)Verify a property link before compliance work (https://pixiecrm.com/help-centre/licence-applications-verify-a-property-link-before-compliance-work)Property and Compliance Monitor integration (https://pixiecrm.com/help-centre/topic/licence-applications-property-compliance)Browse all Licence Applications guides (https://pixiecrm.com/help-centre/category/licence-applications)Customers and contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Client portal (https://pixiecrm.com/help-centre/category/client-portal)Compliance Monitor (https://pixiecrm.com/help-centre/category/compliance-monitor)Real Estate Management (https://pixiecrm.com/help-centre/category/real-estate-management)Letter Manager (https://pixiecrm.com/help-centre/category/letter-manager)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)