No as @stephdl explains you can use groups and user accounts form the nethserver acount provider for this.
As an example you created a group developers in the nethserver admin (Users and Groups > Groups). You added the users who are in this Group (ie John, Marry, Jantje Pietje and Klaasje).
If John is logged in to SOGo he can share his agenda with the group firstname.lastname@example.org. And set acl’s As @stephdl described. Other members of the group have access to John’s agenda.
Note: The ACL is not created automatically, every member of the group has to share its agenda with the group email@example.com. Main reason is, we just use the account provider as an authentication source, with a standard schema. We do not add special property’s to a group to identify what it should do.
This being said with a bit of imagination you can also create resources like a meetingroom1 and meetingroom2 as regular users in the nethserver admin and create a group for it (ie meetingrooms) and add Users to it who are allowed to make reservations.
AGAIN: the meetingroom1 has to login to SOGo once to set the ACLs for sharing with firstname.lastname@example.org.
NOTE: just tested this with Loacal-AD, long time ago did the same with LDAP, not sure if this still works.