Change all employee calendars to read/busy

[David Walton]

Hi folks,

I would like to use GAM to effectively prohibit users in our Google Workspace (or a specific OU) from hiding their calendars.

 

We have an issue with employees hiding their Google calendars, which makes it difficult for staff and administrators to schedule meetings. Despite making free/busy the default and telling employees that they shouldn't hide their calendars, many still do. 

 

Currently, our employee OUs are configured to set calendar sharing free/busy by default, with the option of showing event details to people in the organization...But we want to prohibit users from hiding their calendars entirely. 

I found this documentation: https://pomba.net/2021/05/google-workspace-useful-gam-commands-for-calendar-privacy/

It seems to describe this exact issue: Run the scripts every now and then, users who hide their calendars will have it automatically changed to free/busy, and eventually they'll get the picture.

But the script doesn't seem to work as intended. The Findstr/Grep output doesn't capture the user's email address that would be necessary to update to free/busy. It's just the line with the domain and the calendar status, without the address itself. Of course, I could run the first command, eg:

 

"gam ou_and_children_ns /employee print users fields primaryEmail | gam csv - gam calendar ~primaryEmail showacl > out.txt"

And manually identify users who have hidden their calendar, but that's cumbersome.

Any ideas?

[Ross Scroggs]

David,

With Advanced GAM you can do:

gam ou_and_children_ns /employee add calendaracls primary freebusy domain

What would you want to do if the user already has a domain ACL of reader/writer?

Ross

--
You received this message because you are subscribed to the Google Groups "GAM for Google Workspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/bbfb1001-2c10-49d2-9679-9f2c6377c982n%40googlegroups.com.

--

Ross Scroggs

ross.s...@gmail.com

[David Walton]

Thanks for the reply, Ross!

I should have mentioned that earlier. Ideally I would exclude folks who have made their ACL reader/writer.

At the same time, I think most folks only make their primary calendars available to specific users, not to the entire org. But ideally we would exclude these users and only target those who have made their calendars hidden.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAJkvRS8iVNit2-R5Kwp5zDHSkCW90hRQ2A46W8K1HomJse0%3DAQ%40mail.gmail.com.

--

David Walton

Information Security Analyst

(562) 944-0351 ext. 5165

[Kim Nilsson]

Ross & David, would it even matter if user have set their calendars to free/busy-domain already?

The end goal is to have all calendars free/busy to domain.

No primary calendars should be set to writer-domain - that's just bad practise.

And since we're adding an ACL for domain we're not removing ACLs to individual users.

Feels like nothing bad can happen.