Google Calendar does not notify our service about the changes.
Our service sends requests and commands to Google Calendar.
Periodically polls it for changes.
Therefore, changes to the Bukza calendar may not appear immediately.
However, we always make a preliminary synchronization prior any order is placed, so the overbooking is not possible.
Only orders with time-blocking statuses are sent to the Google Calendar (by default these statuses are "Pending" and "Confirmed").
If you change any dates or statuses, we will immediately send the changes to Google calendar.
We add a special property to our events sent to Google to distinguish our events from your events.
When we receive data from Google Calendar, we skip our events to avoid duplicating them.
The events unloaded from Google are not converted into real reservations, they only block the time on the calendar.
If you change the "not ours" events on the Google Calendar side, they are also updated in the Bukza calendar during synchronization.
But you shouldn't change the events marked with the Bukza tag.
Their change will not affect the original reservations in our system.
Please, note that our service does not handle recurring events in the Google calendar.
If you have recurring events, make this time unavailable in Bukza.
To do this, create an unavailable rule of work.
Specify recurring periods in it. See how to create such a rule here
In the event description, you can add a number in square brackets.
Our system will treat it as the number of reserved shares of the resource - Total share count of the reservation.
If the number of reserved shares is not specified, it is considered that the entire resource has been booked.