Use the Maintenance and supplier controller references
Map client/admin/landlord/supplier requests, jobs, evidence, invoices and payment actions.
Exact navigationMaintenance & Jobs and portals
Before you begin
- Use an account with Relevant staff/client/supplier access 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
Map client/admin/landlord/supplier requests, jobs, evidence, invoices and payment actions. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Maintenance & Jobs and portals.
- 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, choices and supported possibilities
Exact actionUse the Maintenance and supplier controller references
Exact navigationMaintenance & Jobs and portals
Module version1.0.0
Access ruleRelevant staff/client/supplier access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
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
- Supporting table/get-data endpoints belong to the parent workspaces.
- 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 use the maintenance and supplier controller references 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.