Reject or return an individual property
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 choose the supported non-approved status and record the required reason where prompted.
- Use an account with real_property_approval: Approval 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
Choose the supported non-approved status and record the required reason where prompted. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Property Operations → Approvals → open pending property → Reject/Return.
- Go to the record and review the current status, approval chain and supporting files.
- Select the supported status, approval, confirmation or signature action.
- Provide the required reason, decision, signature or attachment when prompted.
- Submit once and verify the new status, approval entry, notification and locked/unlocked actions.
Fields and options
Rules and limits
- Do not invent a status; use only the options displayed by the workspace/controller.
- 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.
Check it worked
- The supported reject or return an individual property 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.
