# Block Booking Permissions in Go Operator

HTML version: [Block Booking Permissions in Go Operator](https://support.gladstonesoftware.cloud/gooperator/block-booking-permissions-in-go-operator)

## Problem
Administrators need to give staff the right Operator role so they can view, create, edit or cancel block bookings and booking exceptions in Centre Management.

## Resolution

1. **Open Permissions in the GMC**
   - Go to `GMC > Security Configuration > Permissions`.

2. **Check each Operator role against the matrix**

   | Permission | Operator Admin: Admin | Operator Admin: Advanced | Operator Standard: Standard | Operator Standard: Limited |
   |---|---|---|---|---|
   | Global | Allow | Deny | Allow | Deny |
   | Centre Management | Allow | Allow | Allow | Deny |
   | Access Centre Management | Allow | Allow | Allow | Allow |
   | Create Block Bookings | Allow | Allow | Allow | Deny |
   | Create Booking Exceptions | Allow | Allow | Allow | Deny |
   | Delete Block Bookings | Allow | Allow | Allow | Deny |
   | Delete Booking Exceptions | Allow | Allow | Allow | Deny |
   | Read Block Bookings | Allow | Allow | Allow | Allow |
   | Read Booking Exceptions | Allow | Allow | Allow | Allow |
   | Update Block Bookings | Allow | Allow | Allow | Deny |
   | Update Booking Exceptions | Allow | Allow | Allow | Deny |
   | Configuration | Allow | Deny | Allow | Deny |
   | Operator | Allow | Deny | Allow | Deny |

3. **Choose the role by what the user needs to do**

   | Role | What it can do |
   |---|---|
   | Operator Admin: Admin | Everything |
   | Operator Admin: Advanced | Centre Management and all Block Booking and Booking Exception actions; no Global, Configuration or Operator settings |
   | Operator Standard: Standard | Everything |
   | Operator Standard: Limited | Open Centre Management and **read** block bookings and exceptions only |

4. **Give each user one role**
   - Assign **one role per user** (see [Assigning and Creating Security Roles in the GMC](../gladstone360/assigning-and-creating-security-roles-in-the-gmc.md)).

## Notes

- **Read** is granted to every role, so any user can open a booking and see its full detail. Seeing detail proves nothing about edit rights.
- **Create / Update / Delete** gate action. Without them, **Edit Booking** and **Cancel Booking** are disabled.
- The **Advanced** column is correct as written (confirmed against the GMC), even though it can look counter-intuitive.
- **One role per user.** A user given both Operator Limited and Operator Advanced had the restrictive role suppress Configuration access entirely. Don't combine roles unless that combination has been tested on that environment.
- [Configuring Access to Centre Management](configuring-access-to-centre-management.md) says a user who already holds Operator Standard or Operator Admin is not affected by also being given Operator Limited. That differs from the case above; until it is confirmed on your environment, keep to one role per user. When a user holds more than one role for the same application, 360 uses the role with the least access ([Gladstone 360 Permission States and Roles](../gladstone360/assigning-and-creating-security-roles-in-the-gmc.md)).
- The **Booking Exceptions** permissions control the **New Exception** tab: see [Creating Booking Exceptions in Centre Management](creating-booking-exceptions-in-centre-management.md).
- *Delete Block Bookings* exists, but the delete flows aren't documented here. Don't infer behaviour from the permission.
- Related: [Block Bookings in Go Operator (Centre Management)](block-bookings-in-go-operator-centre-management.md); [Configuring Access to Centre Management](configuring-access-to-centre-management.md).