Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] replication to Google, Phase 2 ....

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] replication to Google, Phase 2 ....

Chronological Thread 
  • From: Jim Fox <>
  • To: Steven Carmody <>
  • Cc: Grouper-Users <>
  • Subject: Re: [grouper-users] replication to Google, Phase 2 ....
  • Date: Thu, 7 Aug 2014 13:23:42 -0700 (PDT)

Our UI that lets people send their groups to Google includes a setting for "who can send to the group". We always set a "no one can view the membership" flag. I think that was to prevent leaking of membership viewer controls.


On Thu, 7 Aug 2014, Steven Carmody wrote:

Date: Thu, 7 Aug 2014 12:11:51
From: Steven Carmody
To: Grouper-Users
Subject: [grouper-users] replication to Google, Phase 2 ....


Like a growing number of schools, we have implemented a mechanism to replicate group memberships from Grouper to GAE. The initial implementation was very basic, and will create a group in GAE, and then manage the membership on an ongoing basis.

Initially, we were doing this with Course groups, and a small number of department-oriented groups. However, we're in the process of delegating to departments the ability and authority to create and mange groups to meet their local needs. We're discovering that people use groups for different purposes (duh ! ), and that in some cases they would like the properties of the target google group to be set differently from the defaults. This isn't really a surprise, and we expect to see the same sort of requests when we start replicating to AD in the next few weeks.

We're interested in starting a conversation about how to address these requirements. We're wondering whether other campuses have started to develop ways to address these sorts of requirements.

Looking forward to an interesting conversation !

Archive powered by MHonArc 2.6.16.

Top of Page