Customer work, connected.

Help & supportMyAccount
Property and Compliance Monitor integration

Open Licence Applications from Compliance Monitor

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to use the injected administrator shortcut on supported Compliance Monitor pages.

Audience: CRM staffPermission: Edit Licence Applications / technical administratorModule v1.0.0
Jump to steps
Where to goAdmin Area → Compliance Monitor → Licence Applications button
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

Use the injected administrator shortcut on supported Compliance Monitor pages. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to the case or technical integration area described.
  2. Verify the linked property and compatible module/table exist.
  3. Use only exposed UI actions; treat model-only methods as unexposed capabilities.
  4. Check any resulting record against the source property and document.

Fields and options

Hookapp_admin_footer JavaScript button
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

  • Open Licence Applications from Compliance Monitor 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page