Problem/Motivation

Calendar owners need to manage customers for their own calendars without receiving site-wide access to reservations.

Proposed resolution

Add an owner dashboard and per-calendar reservation list. Introduce separate own-calendar permissions for viewing, editing, cancelling, and checking in reservations. Offer an opt-in notification to the calendar owner when reservations change.

Remaining tasks

Implement for the next minor release, add automated coverage, and verify the workflow on a local Drupal site.

Test coverage

Cover owner versus unrelated-calendar access, anonymous access, individual permission combinations, notification recipients and deduplication, and the owner management interface.

Comments

josh.fabean created an issue. See original summary.

josh.fabean’s picture

josh.fabean
Location Florida
commented
Version: 3.1.x-dev » 3.2.x-dev
Status: Active » Fixed

Implemented and pushed to 3.2.x; available in 3.2.x-dev.

  • e72ee7be: Owner dashboard, reservation lists, scoped management permissions, and owner notifications.
  • 23181d2b: Cancellation returns scoped owners to their own reservation workspace.
  • 69e8fb20: Shared workflow infrastructure and upgrade defaults.
  • b5fec2a6: Automated regression coverage and documentation.

Verification: full module suite passes with 91 tests and 1,984 assertions. Coverage includes calendar ownership boundaries, individual permissions, unrelated-user denial, owner notifications, and the management forms. Drupal coding standards and static analysis pass. Run database updates and rebuild caches after updating.

Adding explicit links to the implementation commits and marking fixed.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.