Delete estate-agent staff
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Remove a staff record only after transferring owned records and assignments.
Where to goAdmin Area → Property Operations → My Staff → Delete
Before you start
- Use an account with real_estate_agent_staff: 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 helps you do
Remove a staff record only after transferring owned records and assignments. 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 → My Staff → Delete.
- Go to the exact record and review linked documents, payments, approvals, files and portal visibility.
- Select the supported Delete, Remove, Void or Cancel action.
- Verify 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 and options
Exact actionDelete estate-agent staff
Exact navigationAdmin Area → Property Operations → My Staff → Delete
Module version1.0.0
Access rulereal_estate_agent_staff: 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.
Rules and limits
- Check properties, approvals, requests, notifications and company links first.
- 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 delete estate-agent staff 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.