Troubleshoot a hidden Real Estate menu
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Compare activation, role capabilities, view-own ownership and company context.
Where to goAdmin Area → Setup → Roles and the intended Real Estate menu
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
Compare activation, role capabilities, view-own ownership and company context. 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 → Setup → Roles and the intended Real Estate menu.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields and options
Exact actionTroubleshoot a hidden Real Estate menu
Exact navigationAdmin Area → Setup → Roles and the intended Real Estate menu
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
- Some menu children intentionally change between staff-in-company and non-company contexts.
- Do not grant administrator access merely to bypass a missing capability.
Check it worked
- The supported troubleshoot a hidden real estate menu 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.