Troubleshoot a permission denied message | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/troubleshoot-a-permission-denied-message Publisher: Pixie Technologies LLC Troubleshooting, limitations and technical reference Troubleshoot a permission denied message Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Check capability, view-own ownership, company context and target-record ownership. Audience: CRM staff; Permission: Administrator; Module v1.0.0; Where to goAdmin Area → Setup → Roles and source record 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 Check capability, view-own ownership, company context and target-record ownership. 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 source record. - 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 permission denied message Exact navigationAdmin Area → Setup → Roles and source record 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 - Core customer/staff/invoice permissions may also be required. Check it worked - The supported troubleshoot a permission denied message 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 Troubleshoot a 404 Real Estate page (https://pixiecrm.com/help-centre/troubleshoot-a-404-real-estate-page)Troubleshoot a form validation error (https://pixiecrm.com/help-centre/troubleshoot-a-form-validation-error)Troubleshoot Real Estate activation (https://pixiecrm.com/help-centre/troubleshoot-real-estate-activation)Apply least privilege to Real Estate Management (https://pixiecrm.com/help-centre/apply-least-privilege-to-real-estate-management)Browse all Real Estate Management guides (https://pixiecrm.com/help-centre/category/real-estate-management)Customers Contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)