Where to start
Admin Area → Properties Management / Compliance
Before you begin
Use current navigation after the merger and verify that historical evidence remains accessible through the intended record.
Follow these steps
- Open an existing property, compliance record and protected evidence file from the current menu.
- Compare their references and relationships with the intended business records.
- Replace staff bookmarks with the current merged workspace route.
- For an old recipient link that fails, use the merged record’s supported reissue workflow after checking recipient, purpose and validity.
- Ask the authorised administrator to preserve historical upload locations needed by legacy evidence links.
Check the result
Current staff and recipient journeys use the merged routes and retain access to the correct historical evidence.
If something does not look right
Some old top-level standalone compliance or renewal URLs cannot be intercepted by the single merged module. Reissuing through the supported workflow is preferable to guessing a replacement URL or copying a token into another path.
Questions and answers
Should the old standalone Compliance Monitor stay active?
The combined installer deactivates its old lifecycle after successful setup. Historical files may still be needed; deactivation is different from deletion.
Does uninstall delete business records?
The merged module’s uninstall/deactivation behaviour preserves business data and files.
Should I create a backup as part of this guide?
Follow the organisation’s explicit change-control decision. This documentation update created no backups, archives, snapshots or database dumps.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Use the merged Property & Compliance Management module
- Find every property and compliance workspace
- Use the administrator Quick Actions bar
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.