How are groups handled in SOGo ?

Usage

Configuration

From the version 1.0.2 of SOGo, groups are now supported. Groups have to be defined in an LDAP server and must have an email address. They can be used in SOGo when :

• defining ACLs on calendars and address books
• scheduling meetingsWhen either settings ACLs or scheduling a meeting, a resource (person, group, room, etc.) has to be specified. Upon save, SOGo will lookup the LDAP entry of that particular resource in order to detect if a group was specified. To detect if a group was specified, SOGo will look at the objectClass attributes of the returned entry. If one of the objectClass attribute is equal to group, groupOfNames, groupOfUniqueNames or posixGroup, the entry is considered to be a group.

When scheduling a meeting with a group, SOGo will decompose the group as soon as the event is saved. Groups decomposition consist of fetching the members of the groups - replacing groups with their members in the attendees list.

As an exemple, if you have a “management” group defined in your LDAP server as :

dn: cn=management,ou=groups,dc=inverse,dc=ca
objectClass: top
objectClass: groupOfNames
cn: management
mail: management@inverse.ca
member: cn=bob,ou=people,dc=inverse,dc=ca
member: cn=alice,ou=people,dc=inverse,dc=ca

When you actually add “management@inverse.ca” in the attendee list while creating an event, Bob and Alice will actually receive the invitation and will be present in the attendee list.

Note that the groups support is a work in progress. Support for dynamic groups needs to be added.