Check the declared CRM requirement
Confirm compatibility before activation. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Modules → Licence Applications
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 you’ll accomplish
Confirm compatibility before activation. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to Setup → Modules.
- Find Licence Applications.
- Verify the target CRM meets the declared requirement.
Fields and options to review
Required CRM2.3.* or compatible later release
Module version1.0.0
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-setup-access/
Rules the system enforces
- The supplied hooks/controller enforce this behaviour.
How to confirm it worked
- Check the declared CRM requirement 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.