To book a resource within a neighbourhood, you can still book using our web or mobile applications.
To understand how resource booking is affected by neighbourhood policies for each application type you can check below.
When booking using the map or list view in UMA Vision, if you hover over a resource that has a neighbourhood policy applied you will see information appear on the tool tip related to the teams that are allowed to book that space for the day selected.
If you click on a resource that you don't have access to book, you will receive a message that this resource is assigned to a different team and you aren't able to book.
When booking using the map view, if you tap on a resource that you don't have access to book, you will receive a message that this resource is assigned to a different team and you aren't able to book.
When booking using the list view, any resources that you can't book will be filtered out of the view.
Only the team members/managers will be able to book the room directly from the panel as per the neighbourhood policy.
To enforce this we recommend turning book anonymously off or even turn booking off completely.
Only the team members/managers will be able to book the room directly from the display as per the neighbourhood policy.
You can disable booking from the office map if required.
Office neighbourhoods refer to the various sections or areas within a workplace that are often organised based on departments, teams or functions. Think of them as mini-communities within the larger office space, where groups of colleagues with similar roles or responsibilities work in proximity to one another.
These neighbourhoods serve several purposes:
Collaboration: Colleagues within the same neighbourhood can easily interact and collaborate on projects or tasks, fostering teamwork and innovation.
Resource Sharing: Teams in the same neighbourhood often share resources such as meeting rooms, equipment, or specialised tools, making it convenient for them to access what they need for their work.
Culture and Identity: Each neighbourhood may develop its own unique culture and identity, reflecting the values and dynamics of the teams that inhabit it.
Efficiency: By grouping related teams or departments together, communication and workflow efficiency can be improved, as employees can quickly access the expertise or support they need from nearby colleagues.
In the context of UMA, neighbourhoods are used to create booking policies to allow or restrict employees (within teams) access to certain spaces.
To create a neighbourhood, follow the guide here.
To understand how this affects booking, check here.
Creating a neighbourhood policy only restricts bookings created on UMA's side.
To ensure that your neighbourhood policy matches the one in UMA for bookings created in Microsoft Outlook, some PowerShell commands will need to be run against the associated resources.
The script ensures:
Only specified users can book the resource.
Out-of-policy requests are automatically declined.
No manual approval is required.
In-policy requests are automatically accepted.
Ensure these settings are applied to all relevant resources to enforce consistent booking policies across Microsoft Outlook and UMA.
To ensure that your neighbourhood policy matches the one in UMA for bookings created in Google Workspace, some configuration will need to take place against the associated resources.
Ensure the resource (e.g., meeting room) is created in the Google Admin console.
For detailed steps, refer to Create buildings, features & Calendar resources.
In the Admin console, navigate to Menu > Directory > Buildings and resources > Resource management.
Select the resource you want to manage.
Click on Sharing options.
Under Share with specific people, add the email addresses of the users or groups you want to grant booking permissions to.
Assign them the "Make changes to events" permission.
In the resource's settings, locate the Auto-accept invitations option.
Choose "Auto-accept invitations that do not conflict".
This setting ensures that the resource automatically accepts booking requests from authorised users if there's no scheduling conflict.
By default, resources might inherit the organisation's calendar sharing settings.
To restrict bookings to only specified users:
Ensure that the resource's calendar is not shared with the broader organisation or is set to "See only free/busy (hide details)" for others.
This setup ensures that only users explicitly granted permissions can book the resource, while others cannot.
Have an authorised user attempt to book the resource to confirm that the booking is automatically accepted.
Have an unauthorised user attempt to book the same resource to ensure that the booking is automatically declined.
For more detailed information, you can refer to Google's support documentation on Approving or denying Calendar room & resource bookings.
Ensure these settings are applied to all relevant resources to enforce consistent booking policies across Google Workspace and UMA.