Desk Booking

Open Desks and add each workspace with the New desk form. The desk code is the one required field; alongside it you record the location or floor, optionally assign the desk to an employee chosen from the directory, and set its status to available, occupied or maintenance. The list shows exactly those four columns — Desk, Location, Assigned, Status — with the assignee's name resolved from the employee record and the status rendered as a badge.

Because assignment is a picker over your real employee directory rather than a text box, the register cannot drift into misspelt names or people who no longer exist as typed. A desk with no assignee simply shows a dash.

When someone needs a desk, add a booking: pick the employee, enter the desk code, and set the from and to dates with proper date fields. Each booking carries a status — booked, checked_in, released or cancelled — so the log distinguishes a reservation from a desk actually in use, and a booking that ended normally from one that was called off.

New bookings appear at the top of the list the moment they are saved, and the form clears so the next one can be entered straight away. The table shows Desk, Employee, From, To and Status, which is the whole story of a booking on one line.

Every row on both screens has Edit and Delete actions. The edit dialog re-reads the record each time it opens, so you always amend the current values rather than a stale copy, and a failed save reports the error instead of silently losing the change. Deleting asks for confirmation first.

Statuses do the housekeeping: mark a desk as maintenance while it is out of service, move a booking to released when the person leaves, or to cancelled if the plan changed. Positive states such as booked show as green badges and in-between states such as occupied are visually distinct, so an out-of-date register is easy to spot at a glance.

The Settings page opens on General Setting, where a Booking accordion records how your organisation runs desks: the Booking Mode — Hot Desk, Assigned or Hybrid — the maximum booking length in days (1, 5, 10 or 30), and whether your policy is to auto-release a desk when there is no check-in.

These choices are saved to your organisation's settings with one click, a confirmation appears when the save lands, and the page reads the stored values back every time it opens — so the policy on screen is always the policy on record, shared by everyone who administers the module.

The Locations tab keeps the list of locations and floors as simple named entries — add “3rd Floor”, “Karachi Office” or whatever matches your buildings, and remove entries you no longer use. The list is numbered, stored in your organisation's settings alongside the booking policy, and shows a clear empty state until you add the first entry.

Desk Booking is a tenant-scoped module: organisation roles such as owners, administrators and HR can reach it, while employees on the self-service surface do not see it by default. The sidebar entry and the route guard share a single rule, so a link is never shown that the guard would then refuse.

Finer control comes from Role Templates, where Desk Booking appears as its own module with four forms — Desk Request, Desk Settings, Desk Settings Floor and Desk Settings Room — each carrying individual Add, View Record, Update, Delete and View toggles. Clear a role's every key in the module and that role loses the route entirely; grant a desk form to an individual employee and the module's route opens for them.