Grant a contact Appointments permission
Authorise one customer contact to use the Britixo client appointment area without granting unrelated customer permissions.
What this feature does
Authorise one customer contact to use the Britixo client appointment area without granting unrelated customer permissions. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The module registers an Appointments contact permission in the CRM client permission list.
The client controller checks the signed-in contact and permission before returning appointment pages.
Global client-area enablement and individual contact permission are both required.
Step-by-step workflow
- Open the customer and select the contact.
- Open Permissions.
- Enable Appointments.
- Save the contact.
- Sign in as that contact and verify access.
Important fields and decisions
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 grant access to contacts who should not see appointment details.
- Revoking permission does not cancel appointments.
- Test direct URLs after revocation.
- 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.
