Delete a business-broker company
Remove an unused broker only after checking staff and property requests.
Exact navigationAdmin Area → Property Operations → Business Brokers → Delete
Before you begin
- Use an account with real_business_broker: Delete 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
Remove an unused broker only after checking staff and property requests. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Property Operations → Business Brokers → Delete.
- Open the exact record and review linked documents, payments, approvals, files and portal visibility.
- Choose the supported Delete, Remove, Void or Cancel action.
- Confirm the action only after checking the consequence described below.
- Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction.
Fields, choices and supported possibilities
Exact actionDelete a business-broker company
Exact navigationAdmin Area → Property Operations → Business Brokers → Delete
Module version1.0.0
Access rulereal_business_broker: Delete
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
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
- Preserve commercial and audit evidence before deletion.
- 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 delete a business-broker company 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.
