New Google Groups settings

[Ross Scroggs]

Google released the transition version of the new Google Groups settings this morning.

See these articles:

* https://support.google.com/a/answer/9191148

* https://drive.google.com/file/d/1-ux3z6-hcjsPbhAj_EIwS7cd_emkE-NC/view

I released version 4.65.80 of Advanced GAM this morning; hopefully it should help you evaluate how the new merged settings will work in your environment.

$ gam info group testgroup1 noaliases nogroups nousers

Group: testg...@domain.com

  Group Settings:

    id: 04i7ojhp45xxxyyy

    name: Test Group1

    description:

    directMembersCount: 11

    adminCreated: True

    allowExternalMembers: true

    allowWebPosting: true

    archiveOnly: false

    customFooterText:

    customReplyTo:

    customRolesEnabledForSettingsToBeMerged: false

    defaultMessageDenyNotificationText:

    enableCollaborativeInbox: true

    includeCustomFooter: false

    includeInGlobalAddressList: true

    isArchived: false

    membersCanPostAsTheGroup: false

    messageModerationLevel: MODERATE_NONE

    replyTo: REPLY_TO_IGNORE

    sendMessageDenyNotification: false

    spamModerationLevel: MODERATE

    whoCanContactOwner: ANYONE_CAN_CONTACT

    whoCanJoin: CAN_REQUEST_TO_JOIN

    whoCanLeaveGroup: ALL_MEMBERS_CAN_LEAVE

    whoCanPostMessage: ANYONE_CAN_POST

    whoCanViewGroup: ALL_MEMBERS_CAN_VIEW

    whoCanViewMembership: ALL_MEMBERS_CAN_VIEW

    whoCanDiscoverGroup: ALL_MEMBERS_CAN_DISCOVER

      showInGroupDirectory: false

    whoCanAssistContent: MANAGERS_ONLY

      whoCanAssignTopics: MANAGERS_ONLY

      whoCanEnterFreeFormTags: NONE

      whoCanHideAbuse: NONE

      whoCanMakeTopicsSticky: NONE

      whoCanMarkDuplicate: NONE

      whoCanMarkFavoriteReplyOnAnyTopic: NONE

      whoCanMarkNoResponseNeeded: NONE

      whoCanModifyTagsAndCategories: NONE

      whoCanTakeTopics: NONE

      whoCanUnassignTopic: NONE

      whoCanUnmarkFavoriteReplyOnAnyTopic: NONE

    whoCanModerateContent: OWNERS_AND_MANAGERS

      whoCanApproveMessages: OWNERS_AND_MANAGERS

      whoCanDeleteAnyPost: NONE

      whoCanDeleteTopics: NONE

      whoCanLockTopics: NONE

      whoCanMoveTopicsIn: NONE

      whoCanMoveTopicsOut: NONE

      whoCanPostAnnouncements: NONE

    whoCanModerateMembers: OWNERS_ONLY

      whoCanAdd: ALL_MANAGERS_CAN_ADD

      whoCanApproveMembers: ALL_MANAGERS_CAN_APPROVE

      whoCanBanUsers: OWNERS_ONLY

      whoCanInvite: ALL_MANAGERS_CAN_INVITE

      whoCanModifyMembers: OWNERS_AND_MANAGERS

    Deprecated:

      allowGoogleCommunication: false

      favoriteRepliesOnTop: false

      maxMessageBytes: 25M

      messageDisplayFont: DEFAULT_FONT

      whoCanAddReferences: NONE

      whoCanMarkFavoriteReplyOnOwnTopic: NONE

Ross

--

Ross Scroggs

ross.s...@gmail.com

[Kevin Melillo ✉]

So are these currently read only?  For example...

whoCanBanUsers: OWNERS_ONLY 

How can we modify this to read OWNERS_AND_MANAGERS

 

--
You received this message because you are subscribed to the Google Groups "GAM for G Suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To post to this group, send email to google-ap...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-apps-manager.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAJkvRS9LPj-a2oD-qiQVcyFGEw9-vt1DZx5vp965RjcMDJNaxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Kevin Melillo Electronic Communications Analyst, Information Technology Phone: 732.465.6609 | Mobile: 732-609-4331 Email: k.me...@ieee.org 445 Hoes Lane Piscataway, NJ 08854

[Ross Scroggs]

Kevin,

The newly exposed (as opposed to the forthcoming merged) settings seem to be writeable.

$ gam info group testgroup1 fields whocanmoderatemembers,whocanbanusers nogroups nousers noaliases

Group: testg...@rdschool.org

  Group Settings:

    whoCanModerateMembers: OWNERS_ONLY

      whoCanBanUsers: OWNERS_ONLY

$ gam update group testgroup1 whoCanBanUsers OWNERS_AND_MANAGERS

Group: testg...@rdschool.org, Updated

$ gam info group testgroup1 fields whocanmoderatemembers,whocanbanusers nogroups nousers noaliases

Group: testg...@rdschool.org

  Group Settings:

    whoCanModerateMembers: OWNERS_AND_MANAGERS

      whoCanBanUsers: OWNERS_AND_MANAGERS

Ross

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAKM%3DboZPQu0bcB7Z9F0uWD5JsjOdF0p0qk5dVq-TLBd%2BPCgnQA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Ross Scroggs

ross.s...@gmail.com

[Kevin Melillo ✉]

Whoop!Whooooop!  Yes, this will do nicely...  now I need a report of all of my groups! 

As always thank you Ross.

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

For more options, visit https://groups.google.com/d/optout.

[Ross Scroggs]

Kevin,

gam print groups basic settings > groups.csv

The columns are organized like info group so it is easy to see the relationship between the new merged setting and its constituent settings.

Ross

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAKM%3Dboav3w80%2BpzbYB%3DziCW2crRAyjGwc9_C53DHhz1fd5Bz9g%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Ross Scroggs

ross.s...@gmail.com

[Kevin Melillo ✉]

Yep.  Already got the report and I removed all non-necessary fields.

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

For more options, visit https://groups.google.com/d/optout.

[Ross Scroggs]

Kevin,

If you use the nodeprecated argument, all of the fields that are going way will be omitted.

Ross

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAKM%3Dboau3EkCxJ9j%2Bnz%2BuW47DdG-FWSTAPXZYVHBgkb1jiV%2B%3DA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Ross Scroggs

ross.s...@gmail.com

[Superdave67]

Do we know what the enableCollaborativeInbox value is showing us?  It appears to be a read-only entry, even though I can set it without an error, but not sure what it's representing in regards to the settings of the group.

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox enableCollaborativeInbox: truedavid_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group enableCollaborativeInbox FALSEupdated group dc_tes...@dev.equifax.comdavid_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox enableCollaborativeInbox: truedavid_cunningham@cloudshell:~/bin/gam$

Any ideas?

Thanks,
Dave

[Superdave67]

Cut and pasting didn't go too well...

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox

enableCollaborativeInbox: true

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group enableCollaborativeInbox FALSE

updated group dc_tes...@dev.equifax.com

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox 

enableCollaborativeInbox: true

david_cunningham@cloudshell:~/bin/gam$

[Ross Scroggs]

That option becomes read/write bewteen May 6th and June 3rd. See: https://support.google.com/a/answer/9191148

--

ross.s...@gmail.com

--
You received this message because you are subscribed to the Google Groups "GAM for G Suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To post to this group, send email to google-ap...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-apps-manager.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/62eeb7e5-6a08-41a7-8edd-18d3b5177f1a%40googlegroups.com.

[Superdave67]

Ahh... cool.

Check whether a collaborative inbox will remain turned on for a group. After the Groups settings launch, the API will support turning on collaborative inboxes. Learn more about collaborative inboxes.

 

So when that value is True, what is it telling us?  As opposed to when it's False?  There's not necessarily a checkbox that determines if a group is a CI (other than resetting the group), so it must rely on a multitude of other settings... yes?

Dave

On Thursday, April 18, 2019 at 11:17:45 AM UTC-4, Ross Scroggs wrote:

That option becomes read/write bewteen May 6th and June 3rd. See: https://support.google.com/a/answer/9191148

--

ross....@gmail.com

To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-manager+unsub...@googlegroups.com.

[Ross Scroggs]

Until the switch, it seems to rely on these settings.

whoCanAssignTopics

whoCanMarkNoResponseNeeded

whoCanTakeTopics

whoCanUnassignTopic

On a test group set all of these to NONE; does enableCollaborativeInbox become False?

--

ross.s...@gmail.com

To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.

To post to this group, send email to google-ap...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-apps-manager.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/a99c8c95-f926-4e16-8f4b-50181289f61f%40googlegroups.com.

[Superdave67]

So it does!  Thank you!

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox

 enableCollaborativeInbox: false

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanAssignTopics Members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanMarkNoResponseNeeded Members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanTakeTopics Members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanUnassignTopic Members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox

 enableCollaborativeInbox: true

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanAssignTopics None

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanMarkNoResponseNeeded None

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanTakeTopics None

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanUnassignTopic None

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox

 enableCollaborativeInbox: false

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanAssignTopics members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanMarkNoResponseNeeded members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanTakeTopics members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam update group DC_test_group whoCanUnassignTopic members

updated group dc_tes...@equifx.com

david_cunningham@cloudshell:~/bin/gam$ ./gam info group DC_test_group | grep enableCollaborativeInbox

 enableCollaborativeInbox: true

david_cunningham@cloudshell:~/bin/gam$

On Thursday, April 18, 2019 at 11:38:13 AM UTC-4, Ross Scroggs wrote:

Until the switch, it seems to rely on these settings.

whoCanAssignTopics

whoCanMarkNoResponseNeeded

whoCanTakeTopics

whoCanUnassignTopic

On a test group set all of these to NONE; does enableCollaborativeInbox become False?

--

ross....@gmail.com