Mark or unmark a property favourite
Follow this guide to use the supported favourite action where exposed. 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/client property listing → Favourite control
Before you start
- Use an account with Authorised authenticated user and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What you’ll accomplish
Use the supported favourite action where exposed. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin/client property listing → Favourite control.
- Go to the record and review the current status, approval chain and supporting files.
- Select the supported status, approval, confirmation or signature action.
- Provide the required reason, decision, signature or attachment when prompted.
- Submit once and verify the new status, approval entry, notification and locked/unlocked actions.
Fields and options to review
Exact actionMark or unmark a property favourite
Exact navigationAdmin/client property listing → Favourite control
Module version1.0.0
Access ruleAuthorised authenticated user
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingVerify the property owner/landlord, estate-agent company, listing type, transaction type, privacy and status before saving.
Address and mapComplete address, city, country and latitude/longitude where the map is used.
Commercial valuesCheck price/rent, commission, fees, income/expense values, currency context and availability dates.
Rules the system enforces
- change_favorite receives property ID and status; it does not override listing visibility.
- Property visibility and actions are controlled by real_property view-own/view/create/edit/delete capabilities.
- Property status, account status and approval workspaces are separate from the main listing form.
How to confirm it worked
- The supported mark or unmark a property favourite flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
