Start from Properties Management or Compliance in your workspace header. This retained task guide is part of Property & Compliance Management UK. Older names and version labels describe the inherited guidance.
Read the merger guide · Find the current route · Browse the full library
- Use an account with Authorised application reviewer 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
Select reject and provide a clear client_rejection_reason where required. 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 → Requests & Applications → Tenant Applications → open application → Decision → Reject.
- 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
- Status becomes rejected and should retain decision/audit evidence.
- Public application and onboarding actions use token/record checks and explicit workflow states.
- Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
Check it worked
- The supported reject a tenant application 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 technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Use the merged Property & Compliance Management module
- Find every property and compliance workspace
- Browse the complete merged feature library
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.