Use broker portal notifications
Review, mark one/all read and open notification details. 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 goBroker Portal → Notifications
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
Review, mark one/all read and open notification details. 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.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields and options to review
Exact actionUse broker portal notifications
Exact navigationBroker Portal → Notifications
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.
Rules the system enforces
- The controller supports inline, desktop and all-read actions plus polling/check requests.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
How to confirm it worked
- The supported use broker portal notifications 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.