Rhythm's integration with Higher Logic Thrive Communities enables a real-time sync of your contacts and organizations in Rhythm to Higher Logic communities and security groups.
In this article, we'll explore some basic concepts of this integration and describe the conditions that would cause a contact or organization to be added or removed from a community or a security group in Higher Logic.
For setup instructions, see our Higher Logic Thrive Communities Integration Setup Guide.
Communities
In Higher Logic, an integrated community is a community where members are defined by your data in Rhythm. For instance, every active member in Rhythm is automatically added into an integrated community in Higher Logic. If a member becomes inactive for any reason in Rhythm, they are automatically removed from that integrated community.
Many different types of integrated communities may be created from your Rhythm data. This includes member, chapter member, committee member, event attendee, or opt-in communities.
Higher Logic supports both integrated and non-integrated communities in the same environment. Membership in an integrated community is always determined by the data in Rhythm. Membership in a non-integrated community is solely determined by the configuration in Higher Logic.
Visibility
New integrated communities are private by default in Higher Logic. Because of this feature, Rhythm will always create and maintain membership for all possible integrated communities. You can use the administrative tools in Higher Logic to make an integrated community available to your users at any time, or choose to leave it private indefinitely.
Integration Keys
To determine if a community is integrated or non-integrated, look for the Integration Key value in your Higher Logic administration tools. If a community has any value in that field, it is an integrated community. If there is no value in that field, then it is a non-integrated community.
These integration keys serve no purpose other than to identify the community to the integration software. This field should not be confused with integration keys that are needed to configure and activate the integration.
Types of Integrated Communities
The following integrated communities are automatically created from your Rhythm data. Values in { } are calculated at the time a record is sent to Higher Logic.
| Name | Integration Key | Requirements |
| {your association name} Members | members#{your Rhythm tenant ID} |
Contact
Membership
|
| {chapter name} Members | chapters#{chapter ID} |
Contact
Membership
|
| {section name} Members | sections#{section ID} |
Contact
Membership
|
| {committee name} Members | committees#{committee ID} |
Contact
Committee Membership
|
| {event name} Attendees | eventRegistrations#{event ID} |
Contact
Event Registration
|
| {role name} Contacts | contactRole#{role name} |
Setup
IF Contact Role Communities is set to "all" Contact
IF Contact Role Communities is set to "members" Contact
Membership
|
| {field value} | {field name}#{field value} |
Setup
Contact
|
| {field value} | {field name}#{field value} |
Setup
Organization
|
Security Groups
In Higher Logic, an integrated security group is a security group where members are defined by your data in Rhythm. For instance, every active member in Rhythm is automatically added into an integrated security group in Higher Logic. If a member becomes inactive for any reason in Rhythm, they are automatically removed from that integrated security group.
Many different types of integrated security groups may be created from your Rhythm data. This includes membership, organization, or contact role security groups.
Higher Logic supports both integrated and non-integrated security groups in the same environment. Membership in an integrated security group is always determined by the data in Rhythm. Membership in a non-integrated community is solely determined by the configuration in Higher Logic.
For more information about security groups, please see the Higher Logic documentation.
Integration Keys
To determine if a security group is integrated or non-integrated, look for the Integration Key value in your Higher Logic administration tools. If a security group has any value in that field, it is an integrated security group. If there is no value in that field, then it is a non-integrated security group.
These integration keys serve no purpose other than to identify the security group to the integration software. This field should not be confused with integration keys that are needed to configure and activate the integration.
Types of Integrated Security Groups
The following integrated security groups are automatically created from your Rhythm data. Values in { } are calculated at the time a record is sent to Higher Logic.
| Name | Integration Key | Requirements |
| {your association name} Members | ReceivesMemberBenefits |
Contact
Membership
|
| {type name} Members | members#{type name} |
Contact
Membership
|
| {package name} Package | package#{package name} |
Contact
Membership
|
| {type name} Organizations | organizationType#{type name} |
Organization
|
| {role name} Role | contactRole#{role name} |
Setup
IF Contact Role Communities is set to "all" Contact
IF Contact Role Communities is set to "members" Contact
Membership
|
Comments
0 comments
Please sign in to leave a comment.