Approvals & Calendar

This page describes the approval workflow and the most important frontend views: the utilization calendar and “My Bookings”.

Approval inbox

For approval-required resources, every booking first lands as a pending request (pending). Eligible users see these requests in the approval inbox.

• In the frontend under “Approvals” — visible only to users who may approve for at least one resource. Others see a notice that they have no approval rights.
• In the admin area at /admin/resource-booking/approvals — all open requests across all resources.

Processing a request

Each request shows resource, title, time span, and the requester. You have three actions:

Action	Effect
Approve	The booking becomes confirmed and blocks the time span firmly
Reject	The booking becomes rejected; a reason can be given
View in calendar	Preview of the resource’s weekly occupancy incl. this request

Via View in calendar, an embedded weekly view of the resource in question opens. This lets you check whether the request fits the weekly schedule before deciding — and you can confirm or reject directly from the preview.

1. Open the approval inbox (frontend or admin)
2. Select an open request
3. Optionally: View in calendar to check the week
4. Approve — or Reject with a reason

Hard first-come

First-come applies: as soon as a request is submitted, the time span is blocked for others — even in the pending state. A rejection or cancellation frees the span again.

---

Utilization calendar

The calendar is the module’s main view. It shows one resource in focus, which you select at the top via a type and resource filter.

Structure

• Columns = weekdays — only the schedulable days of the resource
• Rows = times in a 30-minute grid — limited to the resource’s booking window
• Booking blocks colored according to the coloring mode; confirmed bookings full, pending ones dimmed
• Non-bookable times (outside the window) appear greyed out
• Week forward / back via the navigation bar; tapping the date jumps to the current week

Booking

1. Choose type and resource at the top
2. Tap a free cell in the calendar
3. The booking sheet opens, pre-filled with day and start time
4. Adjust start and end (the resource’s duration limits apply)
5. Enter a title — required, so it is recognizable in the calendar what was booked
6. Tap Book or Submit for approval

When changing start/end, the sheet checks live whether the span is free. On a conflict, a message appears and submitting is blocked. If the resource requires approval, a notice indicates that the booking will be submitted for approval.

Login required to book

Booking is a write action and requires a login. If the user is not signed in, login is requested on demand — there is no hard lock of the view.

---

My Bookings

Under “My Bookings”, every logged-in member sees their own requests and bookings.

Status	Meaning	Color
Confirmed	Booking is fixed	Green
Pending	Request is waiting for approval	Yellow
Rejected	Request was rejected (with reason)	Red
Cancelled	Withdrawn by the user	Grey

Pending and confirmed bookings can be cancelled — this frees the span again. For rejected requests, the given reason is shown.

Only with login

“My Bookings” shows only bookings linked to the logged-in account. Without a login, a notice with a login prompt appears.

---

Resource overview

The resource overview in the frontend lists all active resources, grouped by type and searchable. Tapping a resource selects it in the calendar and jumps straight there.