Date: Thu, 28 Mar 2024 23:17:34 +0000 (UTC) Message-ID: <930014328.7175.1711667854391@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7174_167479174.1711667854389" ------=_Part_7174_167479174.1711667854389 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Regroup (htt= p://www.regroup.com/) is a SaaS notification system.
Regroup can be used for:
=E2=80=A2 A Mass Notifications / Emergency Messaging platform that can have=
its group members managed externally. This is done through Regroup=E2=80=
=99s unique feature of membership and messaging APIs
=E2=80=A2 Messaging to people in grouper. e.g. emailing, texting grouper gr=
oups
On July 22, 2015, the Grouper team had a conference call with Regroup to= discuss how Regroup can be integrated with Grouper so that groups in Regro= up can be managed from Grouper.
There are no plans to develop an integration until we have an institutio= n which is a client of Regroup and which uses Grouper and wants to integrat= e the two.
The Regroup API is membership based, there are not operations to update = users without updating memberships. Maybe there should be a feed for = a group of all users which might not be used for notification which manages= the users, emails, phones, etc. Maybe that feed would be outside of = Grouper? Then the Grouper integration can focus on matching up the gr= oups in Regroup with the userIds of users in those groups. Not sure i= f all groups in Regroup would be managed by Grouper or just some of them.= p>