Troubleshoot public booking and Appointments permissions
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Diagnose missing menus, forbidden pages, hidden services and failed public submissions without weakening Pixie CRM access controls.
What you’ll accomplish
Diagnose missing menus, forbidden pages, hidden services and failed public submissions without weakening Pixie CRM access controls. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
Staff menus depend on module permissions, client pages require global enablement plus contact permission, and public services depend on form configuration and eligibility.
The public controller validates fields, terms, reCAPTCHA and live availability before storing a record.
A 403 or hidden action should be traced to the intended access check rather than bypassed.
Follow these steps
- Identify whether the user is staff, a logged-in contact or a guest.
- Check the relevant role/contact/global setting.
- Check service, provider and public-form eligibility.
- Check terms, reCAPTCHA and validation errors.
- Test with a clean browser and inspect server/module logs.
Settings to check
Check it worked
After this workflow completes, Pixie CRM keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Pixie CRM database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Common mistakes to avoid
- Do not make a protected controller public to solve a menu issue.
- Do not disable security checks globally.
- Use an exact test account matching the affected role.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.