The first back-end configuration option "Override property specific settings for Google calendar integration?" needs a little more explanation IMHO.

If in fact the property/front-end setting is NOT enabled, then unless the back-end is set to "Overide..." = "Yes", the Google Calendar Integrator function does not actually function.

Simply setting the back-end "Enabled" = "Yes" is not sufficient to turn the Google Calendar Integrator 'On'.

If the Integrator front-end is not enabled for the property, then the back-end "Overide" should really be ignored and only the back-end "Enabled" be tested for "Yes" to determine whether the Google Calendar Integrator plugin should be active.

In my case I have a single property (www.dreamwoodinternational.com).

Forgive me if this is explained in the manual but I would expect the configuration options to be self sufficent in their meaning to the User.

From my point of view, this makes sense like it`s now.

For example:

If at some point the admin wants to disable the google calendar feature feature for managers, then he can just use the backend and set override to yes and enabled to no, without the need to set enabled-no for each property. This way, no matter what the managers have set up in the plugin config, it will be ignored.

Also, there is a possibility for the admin to disable this feature for managers and instead just use his settings. So he`ll set override to yes and enabled to yes one time from the backend, not for every property.

Ok I guess my view is blinkered by the fact that I am both Admin and (Lone) Manager.

Also I figured that the back-end 'Enabled?' acted as a 'master switch', so that if an Admin wished to turn off the Integrator he would just set back-end 'Enabled?' to "No" - without the need to use the 'Override'setting as part of the 'turn off' procedure.

Actually you set the enabled-yes/no in the backend for nothing if you don`t want to override the frontend settings. So override must be set to yes for the backend admin settings to be active.