...

• Leverage UHIMS's ability to automatically create groups by campus, role, EAC code, academic objective, course enrollment, etc.

• Allow Grouping owners to identify and manage groups of individuals for business purposes, communications purposes, etc.

• Allow Grouping owners to manually augment the Grouping by including or excluding select individuals.

• Allow Grouping owners to publish a Grouping to a LISTSERV list and/or a Google group (or elsewhere in the future).

  • LISTSERV lists Lists and groups are refreshed every 3 minutes.

  • Users that use the LISTSERV feature to option out of a list will trigger a notification email to the owner(s).  An owner can then contact the user.

• Allow Grouping owners to enable members of a Grouping to effectively opt themselves out of the Grouping (e.g.: they no longer want to receive email from the respective list).

• Allow Grouping members to opt in/out (at the Grouping owner's discretion) of the Grouping's publication to external services, such as a LISTSERV list.

• API so that an application developer can automatically populate a Grouping's Include or Exclude group (see below for concepts and the developer documentation for API details).

• Use UH Grouping's uhReleasedGrouping feature so that your group can be used for access control with CAS.

• Use UH Grouping's term transition feature to automatically change the group membership when semesters change.

• Use the UH Grouping's lifecycle feature so that you receive email when a person in your group leaves or changes position, for example, if authorizations need to be revoked.

  • It is very easy to grant access to someone, but it is even easier to forget to remove such access when the person is no longer authorized. UH Groupings can provide that reminder when someone in the group has left or changed positions

  • If an email notification is not appropriate (e.g. need real-time message for automatic deprovisioning), use the UH Message Broker instead. The underlying events that cause a person to enter or leave a group are available as a message.

...

• Nowhere - there is no destination

  • Membership sync'ing of a Grouping to an external resource is optional.

• LISTSERV list

  • A grouping may be synchronized with a single associated LISTSERV list.

  • The LISTSERV list is automatically created and synchronized with your grouping if you answered "yes" to "Publish your Grouping to a LISTSERV list?" (in the UH Groupings Request Form)

  • The name of the LISTSERV list is the name of your grouping without its enclosing folder.  For example, hawaii.edu:custom:test:foo-bar would generate the foo-bar LISTSERV list

  • To send email, be sure to append @ and lists.hawaii.edu after the list name.

  • Please review UH Groupings and LISTSERV Settings to view the default settings for groupings. You can also use it as a guide for requesting different settings for your list.

  • See also UH Groupings and LISTSERV Considerations

• Google group

  • The name of the Google group is the name of your grouping without its enclosing folder.

• CAS/LDAP attribute, uhReleasedGrouping

• Future destinations to be determined

  Google groups tentatively planned for late summer 2022.

  • Atlassian Confluence groups at some point further out.

Developer Information

UH Groupings and Role Based Access Control

...