Create a broker portal buy or rent request
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use Requests or Rent Requests with the selected client/property data.
- Use an account with Authenticated broker user with request capability 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 helps you do
Use Requests or Rent Requests with the selected client/property data. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Broker Portal → Requests / Rent Requests → New.
- Select the New, Add, Create or Start action exposed on that screen.
- Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
- Save or submit the form once; correct any validation message rather than bypassing it.
- Go to the resulting record and verify its number, status, totals, files, activity and downstream links.
Fields and options
Rules and limits
- Request types use separate tables/routes but shared request conversion/PDF/email logic.
- 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.
Check it worked
- The supported create a broker portal buy or rent request 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.
