This article lists the PortalWX permissions of the Bookings 2.0 module – parking spots, hot desks and other bookable items – and what each one lets an administrator do. The older Reservations module (Bookings 1.0) has its own permissions: Reservations (Bookings 1.0) permissions.
The Bookings 2.0 permission
Bookings 2.0 is the module permission. It opens Amenities ▸ Bookings 2.0 and shows the booking assets and their details. Managing assets and managing bookings are two separate sub-permissions – someone can be allowed to create bookings without being able to change the assets.
Important: Bookings 2.0 on its own does not let a person log in to PortalWX. A booking-only administrator also needs one other module permission – for example People or Company.
Sub-permissions
| Permission | What it lets the user do | Notes |
|---|---|---|
| Bookings 2.0 | See the Bookings 2.0 module, the booking assets and asset details. | Module permission – required for everything below. |
| Manage Booking Assets | Add, edit or delete any shared asset – a pool of parking spots, hot desks or similar – that can be booked in the mobile app. | For the administrator who owns the assets. |
| Show Booking Reservations | See all bookings that were made. | Opens the bookings list; read-only. |
| Create Booking Reservations | Create new bookings in PortalWX – without being able to edit or delete them. | |
| Manage Booking Reservations | Create, edit and delete bookings, including other people's. |
Good to know
Whether a company's people can book from the mobile app is the app permission Bookings 2.0 under the company's Permissions for App users.
See also: PortalWX permissions — overview, Which permission do I need for….