Dashboard, reports, notifications and search

Review listing analysis by status

Compare property listings grouped by status.

Audience: CRM staffPermission: real_report: ViewModule v1.0.0
Exact navigationAdmin Area → Reports → Reports → Listing Status
Before you begin
  • Use an account with real_report: View 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 this guide covers

Compare property listings grouped by status. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Reports → Reports → Listing Status.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

Fields, choices and supported possibilities

Exact actionReview listing analysis by status
Exact navigationAdmin Area → Reports → Reports → Listing Status
Module version1.0.0
Access rulereal_report: View
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
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.

Code-backed validations and workflow rules

  • The controller action is report_by_listing_status.
  • Reports require real_report view capability.
  • Report results depend on stored status/date/currency values and the current user’s accessible data.

Expected result and verification

  • The supported review listing analysis by status 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.