Appointments & Scheduling · How-to guide

Understand appointment data, public links and security boundaries

Learn what appointment information is stored, how public hash links work and which actions remain permission-controlled.

Audience: Staff who manage appointmentsFeature: Data and securityModule v1.3.6
Feature pathAppointmentsAppointment record and public appointment URL
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

Learn what appointment information is stored, how public hash links work and which actions remain permission-controlled. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.

How the module flow works

Appointments store customer or external contact details, notes, description, schedule, timezone, status, reminder choices, feedback, recurrence data, files and integration references.

Public appointment pages are accessed with a generated hash and return a not-found response when the hash does not resolve to a record.

Staff controller actions check staff permissions; client portal actions verify that the appointment belongs to the logged-in customer; invoice conversion also requires invoice Create permission.

Step-by-step workflow

  1. Restrict staff roles to the minimum required capability.
  2. Share public appointment links only with the intended participant.
  3. Avoid placing private staff notes in the public description field.
  4. Use client portal contact permission for authenticated access.
  5. Review provider email and phone visibility before enabling them on the public form.
  6. Use deletion only when retention requirements permit it.

Important fields and decisions

Private notesStaff-only operational notes stored on the appointment.
DescriptionSession overview that may be included in notifications and calendar events.
Public hashUnpredictable token used for the customer-facing appointment page.
Contact permissionControls authenticated customer access to Appointments.
Calendar linksCan expose meeting and attendee information to the connected calendar service.

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 email a public link to the wrong recipient.
  • Treat exported ICS files as containing appointment details.
  • Keep calendar OAuth credentials and tokens restricted.
  • Use activity history and notes for accountable changes.
  • 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.