Create a buy request from the client portal
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Allow a customer to submit the buy request form.
Where to goClient Portal → Real Estate → Buy Application
Before you start
- Use an account with Authenticated 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 helps you do
Allow a customer to submit the buy request form. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Client Portal → Real Estate → Buy Application.
- 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
Exact actionCreate a buy request from the client portal
Exact navigationClient Portal → Real Estate → Buy Application
Module version1.0.0
Access ruleAuthenticated 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.
ConversionCheck status and linked customer/property before converting to a contract or invoice.
Rules and limits
- The client controller property_request defaults request_type to buy and uses the current customer context.
- 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.
Check it worked
- The supported create a buy request from the client portal 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.
Related guides
Was this guide useful?Your response is stored only in this browser.