Send property, request, contract, invoice, payment and maintenance emails
Use the send action from the source record.
Exact navigationAdmin Area/Broker Portal → open source record → Send Email
Before you begin
- Use an account with Relevant record 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
Use the send action from the source record. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area/Broker Portal → open source record → Send Email.
- Open the source record and verify its recipient, status, totals and attachments.
- Choose the Send, Email, Share or Request action described in the guide.
- Select recipients and attachment/signature options shown by the form.
- Submit once and verify the activity, delivery metadata, public link or approval request created by the module.
Fields, choices and supported possibilities
Exact actionSend property, request, contract, invoice, payment and maintenance emails
Exact navigationAdmin Area/Broker Portal → open source record → Send Email
Module version1.0.0
Access ruleRelevant record access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingConfirm the property owner/landlord, estate-agent company, listing type, transaction type, privacy and status before saving.
Address and mapComplete address, city, country and latitude/longitude where the map is used.
Commercial valuesReview price/rent, commission, fees, income/expense values, currency context and availability dates.
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.
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.
Financial recordClient/vendor/landlord, linked property/request/contract, date/due date, currency, items, taxes, discounts, totals and status.
Payment evidencePayment mode, amount, transaction ID, note/comments, date paid and email/PDF choices where exposed.
Code-backed validations and workflow rules
- The module relies on global SMTP and source-specific recipients/attachments.
- Property visibility and actions are controlled by real_property view-own/view/create/edit/delete capabilities.
- Property status, account status and approval workspaces are separate from the main listing form.
- 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.
- 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.
- Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
- The module hooks after_payment_added to write property-related activity when the payment is linked.
Expected result and verification
- The supported send property, request, contract, invoice, payment and maintenance emails 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.