Edit or delete a Real Estate plan
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Maintain plan limits and role mapping or remove an unused plan.
Where to goAdmin Area → Settings → General Settings → Plans
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 this guide helps you do
Maintain plan limits and role mapping or remove an unused plan. 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 → Plans.
- 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
Exact actionEdit or delete a Real Estate plan
Exact navigationAdmin Area → Settings → General Settings → Plans
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 and limits
- Check linked companies before deletion.
- Read-only plans should not be treated as freely editable by users.
Check it worked
- The supported edit or delete a real estate plan 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.