we have a client with extremely large floorplates, which appear in serraview as level Zone A and Zone B. in their VBS data they have a large neighborhood, which is set up as two neighborhoods in VBS. for static reporting this limitation is acceptable. But this has an impact on booking experience of Engage. teams in this neighboorhood, can in fact work on either side of the core, if they chose. how can engage and or vbs, be configured so the booking expeirence - working within a neighborhood over two cores, be configured when this is treated separately in VBS. As a staff member i want to book a seat in either my neighborhood in zone A or B. but booking by "floor" is not an option as this opens up the bookings to other teams not in my neighborhood.