Edit a Real Estate role and propagate permissions
Follow this guide to update role values and choose whether linked staff permissions are updated. 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 → Settings → General Settings → Roles → Edit
Before you start
- Use an account with Administrator 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
Update role values and choose whether linked staff permissions are updated. 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 → Settings → General Settings → Roles → Edit.
- Go to the intended record from the list or preview.
- Select Edit and change only the required fields.
- Save once and resolve any validation or permission message.
- Reopen the record and verify the update, status and audit/activity evidence.
Fields and options to review
Exact actionEdit a Real Estate role and propagate permissions
Exact navigationAdmin Area → Settings → General Settings → Roles → Edit
Module version1.0.0
Access ruleAdministrator
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Rules the system enforces
- Check the update_staff_permissions choice before saving.
How to confirm it worked
- The supported edit a real estate role and propagate permissions 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.