Activate or deactivate estate-agent staff
Change the staff active status through the supported status action. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Property Operations → My Staff → Status
Before you start
- Use an account with real_estate_agent_staff: Edit 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 you’ll accomplish
Change the staff active status through the supported status action. 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 → Status.
- Find Real Estate Management in the module list and review the displayed version and CRM requirement.
- Select Activate and allow the module lifecycle hook to complete.
- Reload the admin area and open the module workspace shown in this guide.
- Verify that the expected settings, menus and records are available before production use.
Fields and options to review
Exact actionActivate or deactivate estate-agent staff
Exact navigationAdmin Area → Property Operations → My Staff → Status
Module version1.0.0
Access rulereal_estate_agent_staff: Edit
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 the system enforces
- Inactive staff should no longer authenticate or act through their prior session after normal CRM handling.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
How to confirm it worked
- The supported activate or deactivate 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.