Convert a broker request to contract
Create a CRM contract from an eligible request.
Exact navigationBroker Portal → Requests → open request → Convert to Contract
Before you begin
- Use an account with Authenticated broker user with request edit/conversion 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
Create a CRM contract from an eligible request. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Broker Portal → Requests → open request → Convert to Contract.
- Select the exact record or option described in this guide.
- Complete the displayed fields or action using the rules below.
- Save or submit once and resolve any validation response.
- Verify the resulting record, status, file, notification or integration effect.
Fields, choices and supported possibilities
Exact actionConvert a broker request to contract
Exact navigationBroker Portal → Requests → open request → Convert to Contract
Module version1.0.0
Access ruleAuthenticated broker user with request edit/conversion access
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.
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.
Code-backed validations and workflow rules
- Verify customer, property, price, term and status first.
- 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.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
Expected result and verification
- The supported convert a broker request to contract 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.