Let hosts override guest rescheduling limits without overlapping events #61

New Issue

2026-09-01T18:49:23Z

eleith commented

2026-09-01 18:49:23 +00:00

Goal

Let the host knowingly reschedule an appointment outside restrictions intended for guests, while still preventing real event overlaps.

Scope

Host-initiated rescheduling only.
Allow deliberate exceptions to guest-facing limits such as daily meeting limits, padding/buffer windows, and normal availability windows.
Make it clear when the chosen time overrides a guest-facing restriction.
Continue rejecting overlaps with other actual appointments and busy calendar events. Ignoring a buffer is not permission to double-book.
Keep the host time-selection UI and server-side validation consistent.
Keep guest booking and rescheduling restrictions unchanged.

Boundaries

Identify any other guest-only restrictions, such as notice, booking horizon or slot spacing, during refinement rather than blindly disabling all validation. Authentication, appointment-state checks and valid time ranges remain required.

Out of scope

Guest requests for scheduling exceptions.
Changes to new-appointment creation or a general scheduling-rule framework.

This retains the host-only scope from the discussion around #62. The separate guest-initiated padding-exception proposal is not being pursued.

## Goal Let the host knowingly reschedule an appointment outside restrictions intended for guests, while still preventing real event overlaps. ## Scope - Host-initiated rescheduling only. - Allow deliberate exceptions to guest-facing limits such as daily meeting limits, padding/buffer windows, and normal availability windows. - Make it clear when the chosen time overrides a guest-facing restriction. - Continue rejecting overlaps with other actual appointments and busy calendar events. Ignoring a buffer is not permission to double-book. - Keep the host time-selection UI and server-side validation consistent. - Keep guest booking and rescheduling restrictions unchanged. ## Boundaries Identify any other guest-only restrictions, such as notice, booking horizon or slot spacing, during refinement rather than blindly disabling all validation. Authentication, appointment-state checks and valid time ranges remain required. ## Out of scope - Guest requests for scheduling exceptions. - Changes to new-appointment creation or a general scheduling-rule framework. This retains the host-only scope from the discussion around #62. The separate guest-initiated padding-exception proposal is not being pursued.

eleith added the enhancement label 2026-09-01 18:49:40 +00:00

eleith-gitea-agent Bot changed title from ~~admin flexibility in rescheduling~~ to Let hosts override guest rescheduling limits without overlapping events

2026-10-23 13:27:07 +00:00

eleith-gitea-agent Bot referenced this issue

2026-10-23 13:27:07 +00:00

allow accepted appointments to be adjusted avoid padding windows #62

eleith-gitea-agent Bot commented

2026-10-23 14:17:15 +00:00

Closing at the owner's request. We are not adding a general host scheduling-rule bypass or an admin-only meeting type as a universal fallback.

Suggested workarounds:

Calendar escape hatch: create an independent event directly in the host's calendar for ad-hoc arrangements, including times or overlaps that When does not offer. When can import it as busy after refresh if that calendar is configured as a conflict source.
Configured booking: for repeatable arrangements that benefit from When's guest workflow, use an existing suitable meeting type and its configured duration choices. An unlisted type can have broader availability and reduced guest restrictions, but unlisted is not access-controlled/private.

Editing a When-created calendar event is not two-way synchronization: When's stored times do not change, and a later When update may overwrite the manual edit.

Closing at the owner's request. We are not adding a general host scheduling-rule bypass or an admin-only meeting type as a universal fallback. Suggested workarounds: - **Calendar escape hatch:** create an independent event directly in the host's calendar for ad-hoc arrangements, including times or overlaps that When does not offer. When can import it as busy after refresh if that calendar is configured as a conflict source. - **Configured booking:** for repeatable arrangements that benefit from When's guest workflow, use an existing suitable meeting type and its configured duration choices. An unlisted type can have broader availability and reduced guest restrictions, but unlisted is not access-controlled/private. Editing a When-created calendar event is not two-way synchronization: When's stored times do not change, and a later When update may overwrite the manual edit.

eleith-gitea-agent Bot closed this issue

2026-10-23 14:17:15 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: eleith/when#61