Britixo CRMBritixo CRM Enterprise Help Centre
Appointments & Scheduling · How-to guide

Troubleshoot public booking and Appointments permissions

Diagnose missing menus, forbidden pages, hidden services and failed public submissions without weakening Britixo access controls.

Audience: Staff who manage appointmentsFeature: Access troubleshootingModule v1.3.6
Feature pathAppointments settings / Staff roles / Contact permissions / Public form
Before you beginThis guide follows the supplied Britixo Appointments & Scheduling module version 1.3.6. The relevant access is Appointments: View. A menu, button, provider, time slot or client action can remain hidden when the signed-in user lacks the required permission, the module setting is disabled, the related record is in an ineligible state, or availability validation rejects the request.

What this feature does

Diagnose missing menus, forbidden pages, hidden services and failed public submissions without weakening Britixo access controls. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.

How the module flow 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.

Step-by-step workflow

  1. Identify whether the user is staff, a logged-in contact or a guest.
  2. Check the relevant role/contact/global setting.
  3. Check service, provider and public-form eligibility.
  4. Review terms, reCAPTCHA and validation errors.
  5. Test with a clean browser and inspect server/module logs.

Important fields and decisions

Staff permissionView, Create, Edit, Delete, Approve or View Reports.
Contact permissionClient Appointments access.
Public configurationGuest access and selected services.
ValidationRequired fields, verification and slot recheck.

What happens after completion

After this workflow completes, Britixo 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 Britixo 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.

Controls, checks and common mistakes

  • 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.
Scheduling and data safetyAppointment changes can notify customers, reserve provider time, update remote calendars, create meeting links or invoices and alter reports. Confirm the exact record, timezone, status and recipients before saving.
Browse connected topics:booking formclient portalserviceproviderinvoicepaymentcheckreportapprovalappointmentschedulingavailabilityremindersfeedback
Enable Appointments permissions →Grant a contact Appointments permission →Public booking form overview →Troubleshoot service and provider availability →Use Appointments history →Edit appointment history notes →Use the Appointments analytics dashboard →Filter appointment reports by date range →