Grant a contact Appointments permission
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Authorise one customer contact to use the Pixie CRM client appointment area without granting unrelated customer permissions.
What you’ll accomplish
Authorise one customer contact to use the Pixie CRM client appointment area without granting unrelated customer permissions. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it 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.
Follow these steps
- Go to the customer and select the contact.
- Go to Permissions.
- Enable Appointments.
- Save the contact.
- Sign in as that contact and verify access.
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 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.