[Feature] Per-appointment permission overrides

[Bytrider]

Hi,

thank you for this great app.

We are currently using it in an organization where multiple members should be able to create appointments, but we need more granular control over visibility and access per appointment.

Current situation

The app already provides global permission settings in the admin configuration, such as:

• who can manage appointments
• who can access check-in
• who can see responses and summaries
• who can see comments

However, these settings apply globally to all appointments and cannot be adjusted per appointment.

Problem

This makes it difficult to:

• allow all members to create appointments
• while restricting access to responses, comments, or attendance data for specific appointments

In our use case, this leads to too much visibility, as all users in certain groups automatically see everything for all appointments.

Feature request

Introduce per-appointment permission overrides, based on the existing global settings.

Concept

• Admin settings define global default permissions
• Each appointment can optionally define custom permissions
• If no custom settings are defined → global defaults apply
• If custom settings are defined → they override the global defaults for that appointment

Configurable per appointment

For each appointment, it should be possible to define:

• Who can see the appointment
• Who can see responses
• Who can see comments
• Who can edit the appointment
• Who can access attendance / check-in management
• Who can self check-in

Permission targets

Permissions could be assigned to:

• appointment creator
• selected users
• selected groups
• admins
• (optional) inherited defaults

Example use case

• Global settings:

  • All members can create appointments
  • Certain groups can see responses and comments by default

• Appointment-specific behavior:

  • A member creates an appointment
  • If no custom settings are configured → global rules apply
  • If custom settings are defined:
    • Only selected users/groups can see responses and comments
    • Even groups that normally have access can be excluded for this specific appointment

Benefit

• Enables delegated appointment creation for all members
• Protects sensitive data on a per-appointment basis
• Builds on the existing permission system instead of replacing it
• Provides flexibility without increasing complexity for standard use cases

Summary

The goal is to combine:

• simple global defaults (admin level)
• flexible per-appointment overrides

This would make the app much more suitable for real-world organizational use.

Thanks for considering this feature.

Berechtigungs Diagramm.drawio

[luflow]

@Bytrider Interesting idea, would bloat the UI quite a bit though - because on each create/edit form you need now the settings of the admin settings - maybe in a collapsible for "Permission overrides"?

Also I would have to split create/edit/delete to make it work (currently its "manage" which includes all three permissions)

Also: A user that can create appointments then could also decide by himself to change the settings to "I want to see comments" and "I want to see responses" - is this correct? Seems like a contradiction to the admin rules to me in this case where you want to be very restrictive and only allow some users to have these rights.

Looking forward to your feedback :)

[Bytrider]

Thanks for the feedback — yes, I agree that this should not bypass or weaken the admin rules.

What I had in mind is not that every user who can create appointments should automatically be allowed to grant themselves access to responses or comments.

Instead, I think this could work as a controlled override model:

• Admin settings remain the global defaults
• Admins can decide which permission fields are allowed to be overridden per appointment
• Appointment creators can only change those specific fields if that is allowed by the admin configuration
• If no appointment-specific settings are defined, the global admin defaults apply

So for example:

• All members may be allowed to create appointments
• But only some permission fields are overridable per appointment
• Sensitive permissions such as “see responses” or “see comments” could remain locked by admin settings unless explicitly allowed

This would avoid contradicting the admin rules while still allowing more flexibility for real-world use cases.

Regarding the UI: yes, I think a collapsible section such as “Permission overrides” would make sense, so the form stays compact unless custom settings are needed.

Also agreed on splitting “manage” into create / edit / delete if per-appointment permissions should become more granular.

My main use case is:

• many users should be able to create appointments
• global defaults should remain simple
• but for specific appointments, selected visibility/access settings should be overridable in a controlled way

For example:

• all members can create appointments
• by default, group-based admin settings apply
• for a specific appointment, the creator may restrict who can see the appointment, comments, or responses — but only if that kind of override is allowed by admin settings

I hope this clarifies the idea better.

[luflow]

Thanks for the detailed spec and diagram @Bytrider! To narrow scope and find a good starting point, a few questions:

1. Single highest-value override: If we had to pick just one permission field to make overridable per-appointment, which would unlock the most value for your org — "who can see responses", "who can see comments", or "who can see the appointment itself"?

2. Admin control model: Confirming: admins tick which fields are overridable (default all off) → creators can only adjust those fields → if admins don't enable anything, behavior is identical to today. Does that match your expectation?

3. Concrete scenario: Could you share one real appointment from your workflow where the current global settings fall short, and describe the exact override needed? Designing from a concrete case beats designing for the general matrix.