The re:Members (Impexium) integration with Higher Logic Thrive Community (Thrive Community) and Higher Logic Community connects your re:Members (Impexium) AMS database with your Higher Logic community site. The integration simplifies the alignment and management of member profile, membership, organization, community, and event information across both systems.
These data are kept current by two refresh processes:
- Periodic Refresh checks re:Members (Impexium) for records that have changed.
- Member Refresh performs a full refresh of each database record that has changed so that Higher Logic has the latest available member data.
These refresh processes help ensure that your community site reflects the most current:
- member information,
- access rules,
- community memberships, and
- event data.
NOTE: Your Higher Logic project team will configure your unique integration based on the completed technical worksheet and validated re:Members (Impexium) API access. Higher Logic cannot set up your integration until the technical worksheet is complete and API access has been validated.
Benefits of the integration
The integration makes it easier to keep your community data aligned with your AMS data.
By syncing contact records, membership access, organizations, demographics, communities, events, and SSO details, Higher Logic can provide a more current and personalized member experience while reducing duplicate administrative work.
Supported features and data
The integration supports the following data and configuration areas, depending on your implementation choices.
- Contact profile sync
- Organization/company record sync
- Membership-based security groups
- Security role-based security groups
- Relationship-based security groups
- Custom demographics
- Committee-based communities
- Membership-based communities
- Event registration-based communities
- Custom field-based communities
- Calendar event sync
- Single Sign-On (SSO)
API access requirements
To begin setup, Higher Logic requires re:Members (Impexium) API access information. Your organization should work with your re:Members (Impexium) Project Manager to provide the following to Higher Logic.
- API URL
- App ID
- App Password
- API-user email address
- API-user password
Contact Profile Sync
Higher Logic can sync standard member contact information (such as name, email address, company, and address) from re:Members (Impexium). Optional profile-related data, such as those listed below, can also be configured to be synced.
- Bios
- Profile photos
- Social media links (e.g., LinkedIn and Facebook)
- Directory visibility preferences from the re:Members (Impexium) ShowInDirectory field
- When directory visibility is enabled, Higher Logic uses the value in the ShowInDirectory field to determine whether a contact should display in the Member Directory in the community.
Organization Sync
Organizations your integrated database can be created as company records in Higher Logic. When enabled, individual records are associated with their primary organization from re:Members (Impexium).
This is useful when your community relies on company affiliations, organizational membership structures, or Company Directory for organizations.
Custom Demographics
Custom demographics fields from your integrated database can configured to be synced to Higher Logic. These fields are commonly used to display member information on profiles or to support Higher Logic automation rules. Some common custom demographics fields are:
- Industry
- Areas of interest
- Education or certifications
- Region or language
Your worksheet should identify:
- each demographic field,
- where it comes from in re:Members (Impexium), and
- the field type.
Member Access and Security Groups
Higher Logic uses security groups to control access to various areas and pages of the community site; this allows Admins to configure member-only experiences. This integration can create and populate security groups based on:
- Memberships
- Security Roles
- Relationships
Security groups may also be used to grant member status (isMember) in Higher Logic.
Membership Expiration and Grace Periods
If enabled, Higher Logic can use the re:Members (Impexium) GraceExpireDate field as the end date for membership-based access. This allows organizations to honor grace periods when determining how long a member retains access.
Communities
This integration can create and populate Higher Logic communities from several re:Members (Impexium) data sources.
Committee-based communities
Members are added based on committee data from your external database.
Membership-based communities
Membership data can optionally be used to create communities and assign members to them based on their re:Members (Impexium) membership information.
Event registration-based communities
Members are added to Event communities based on event registration data from re:Members (Impexium).
Custom field-based communities
Custom fields can also be used to create communities, which is helpful when your organization groups members by interests, categories, or other structured data maintained in re:Members (Impexium).
Calendar Event Sync
Events in re:Members (Impexium) can be synced to Higher Logic and displayed on your community site.
Only public events are included in the sync.
Event data should be maintained in re:Members (Impexium) because synced fields may be overwritten in Higher Logic during future refreshes.
Single Sign-On
re:Members (Impexium) AMS supports single sign-on with Higher Logic. With SSO, members can move between your organization's main website and your Higher Logic community without logging in separately to each system.
For setup and validation, Higher Logic requires test login credentials and the associated re:Members (Impexium) Customer ID (GUID).
Customer responsibilities
To support a smooth implementation, your organization should:
- Complete the re:Members (Impexium) AMS technical worksheet.
- Ensure API credentials are active and correct.
- Confirm whether organizations should sync as company records.
- Confirm which profile, membership, security group, demographic, community, and event features should be enabled.
- Ensure event records intended for sync are public in re:Members (Impexium).
- Provide SSO test user credentials.
Implementation checklist
| Feature / Data | Required Information |
|---|---|
| API Access | API URL, App ID, App Password, API-user email address, API-user password |
| Contact Sync | Profile fields and optional profile data to sync |
| Organizations | Will organization records sync as company records? |
| Custom Demographics | Demographic names, source fields, and field types |
| Security Groups | Types that will sync (Memberships, Security Roles, Relationships) |
| Membership Access | Will Higher Logic use the membership grace period from re:Members (Impexium) for membership expiration |
| Communities | Committees, memberships, event registrations, and/or custom fields |
| Calendar Events | Ensure event records intended for sync are public in re:Members (Impexium) |
| Single sign-on (SSO) | Test the username, password, and re:Members (Impexium) Customer ID |
Important notes
- re:Members (Impexium) is the source of truth for integrated profile, membership, organization, event, and community-related data.
- Some options are available only when the corresponding data is present and consistently maintained in re:Members (Impexium).
- Higher Logic cannot set up the integration until API access is validated.