Maintenance requests and tenant feedback

Upload maintenance photos

Attach supported images to evidence the issue.

Audience: CRM staffPermission: Authenticated tenant/client contactModule v1.0.0
Exact navigationClient Portal → Real Estate → Maintenance → New Request → Photos
Before you begin
  • Use an account with Authenticated tenant/client contact 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

Attach supported images to evidence the issue. 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 Client Portal → Real Estate → Maintenance → New Request → Photos.
  2. Download or inspect the supported template/field requirements before preparing the file.
  3. Choose the Import or Upload action and select the intended file only.
  4. Run validation and correct rejected rows, file types or required values.
  5. Complete the import/upload and review the created records, attachments and any error file.

Fields, choices and supported possibilities

Exact actionUpload maintenance photos
Exact navigationClient Portal → Real Estate → Maintenance → New Request → Photos
Module version1.0.0
Access ruleAuthenticated tenant/client contact
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionReview status and linked customer/property before converting to a contract or invoice.
Tenant/applicantIdentity, contact, current address, employment/income, occupants, pets, smoker/benefits/children flags and right-to-rent data where exposed.
Tenancy termsProperty, tenant client, start/end/move-in dates, term, rent, frequency, deposit, holding deposit and deposit scheme.
Consent and workflowInvite mode, consents, review notes, agreement template/body, signature stage and workflow action.
Maintenance requestProperty, tenant, subject/issue, priority, status, supplier, assignee, cost and administrative note.
Supplier work orderJob title/description, property/manual address, allocated amount, supplier notes, photos and completion evidence.
Financial linkSupplier invoice status, amount/final amount, payment mode, transaction ID and payment comments.

Code-backed validations and workflow rules

  • The client form supports photos[]; remove sensitive/unrelated content.
  • Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
  • Status changes and conversion actions validate the current request and linked record IDs.
  • Public application and onboarding actions use token/record checks and explicit workflow states.
  • Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
  • Maintenance hub visibility is tied to customer-view access in the registered menu.
  • Supplier completion can create a Pending supplier invoice when one does not already exist.

Expected result and verification

  • The supported upload maintenance photos 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.