Dashboard, reports, notifications and search

Mark a broker notification read

Follow this guide to use inline/desktop/read controls. 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.

Audience: CRM staffPermission: Authenticated broker userModule v1.0.0

Jump to steps

Where to goBroker Portal → Notifications → notification

Before you start

Use an account with Authenticated broker 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 inline/desktop/read controls. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Broker Portal → Notifications → notification.
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 a broker notification read

Exact navigationBroker Portal → Notifications → notification

Module version1.0.0

Access ruleAuthenticated broker user

VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.

Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.

Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.

Report filtersSelect the displayed month/year/custom period, status, property type, city, listing or payment criteria.

Source verificationOpen source property, request, tenancy, contract, invoice or payment records to reconcile totals.

Rules the system enforces

Single/all-read actions update stored notification state.
Company, owner, broker and staff records use different capability groups and ownership checks.
Email-exists checks prevent duplicate staff/company identities in supported forms.
Reports require real_report view capability.
Report results depend on stored status/date/currency values and the current user’s accessible data.

How to confirm it worked

The supported mark a broker notification read 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.

Was this guide useful?Your response is stored only in this browser.