Understand Property & Compliance Management uninstall risk
Do not run uninstall without reviewing the supplied uninstall behaviour and preserving records/files.
Before you start
Use an administrator account for activation and General Settings.
Follow these steps
- Open the module or settings page named in Where to go.
- Do not run uninstall without reviewing the supplied uninstall behaviour and preserving records/files.
- The installed uninstall handler deliberately retains business tables, evidence, uploads, current-workspace options and additive CRM columns. Uninstalling removes module availability; it is not a data-erasure action. Retention/purge requires a separate authorised workflow.
- The intended module or setting is active in this workspace; related menus open with the appropriate staff account.
Fields, rules and limits
- The installed uninstall handler deliberately retains business tables, evidence, uploads, current-workspace options and additive CRM columns. Uninstalling removes module availability; it is not a data-erasure action. Retention/purge requires a separate authorised workflow.
Check it worked
The intended module or setting is active in this workspace; related menus open with the appropriate staff account.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
What should I verify for this task?
The installed uninstall handler deliberately retains business tables, evidence, uploads, current-workspace options and additive CRM columns. Uninstalling removes module availability; it is not a data-erasure action. Retention/purge requires a separate authorised workflow.
Why is the record or action unavailable?
Use an administrator account for activation and General Settings. Check the current company and record relationship before requesting additional access.