COmanage Developers List

[Chris Hyzer <>]

There have been postings to the users list periodically about how people have 
set it up... generally it is up to the institution.  Some things to keep in 
mind:

Folders are used for:

1. Privileges.  You can delegate access to create groups and folders down the 
folder hierarchy
2. Filtering groups.  i.e. for an application, if all the groups used in that 
application are in a folder, then you can easily get a group list or 
membership list for the entire application in one WS call
3. Hierarchies in memberships.  You can have a loader job which rolls up 
memberships in child orgs into a parent org which could be in a parent folder
4. Soon to be to restrict which subjects are allowed to be used in 
groups/permission (i.e. in folder "apps", only employees can be assigned to 
groups)

Here are some threads:

https://lists.internet2.edu/sympa/arc/grouper-users/2010-04/msg00018.html

https://lists.internet2.edu/sympa/arc/grouper-users/2010-04/msg00035.html

https://lists.internet2.edu/sympa/arc/grouper-users/2010-05/msg00013.html

https://lists.internet2.edu/sympa/arc/grouper-users/2011-01/msg00004.html

Thanks,
Chris



-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of heather flanagan
Sent: Wednesday, February 09, 2011 1:41 PM
To: CoMaNaGe-DeV List
Subject: [comanage-dev] documentation on planning for a new group namespace?

Hi all -

I'm hunting through the Grouper site to see if there is any
documentation on what an entirely new org might want to consider when
it comes to establishing the namespace and potential hierarchies for
their group environment.  I'm not seeing anything right off the bat,
and wonder if anyone here knows of a document of that nature?

Thanks!

-hf