NOTE: This Higher Logic Technical Worksheet is intended for customers with Engagement Platform for Members.
The technical integration framework between your Association Management System (AMS) and Higher Logic is determined by the information received in this technical worksheet. This framework defines how Higher Logic interacts with the data in your AMS to create:
- member profiles,
- security groups,
- communities, and
After the integration is established, a periodic check (Periodic Refresh) for changed records in your AMS, coupled with a refresh of each updated record (Member Refresh) yields a robustly integrated ecosystem. The Periodic Refresh and Member Refresh ensure that Higher Logic has the most-up-to-date member data.
Complete the information below, providing as much detail as possible. Contact your project manager if you have any questions.
Section I: Web service access
To start the integration, provide the following access credentials for your AMS to Higher Logic.
|Database server URL|
Section II: Membership status
This integration syncs all records from MemberClicks (Oasis) to your Community site.
List the Member Type Codes that exist in MemberClicks (Oasis). For each, also include the API GUID of one user with that Member Type Code.
|Member Type Code||Access to Site?||Access to Open Forum/
Show in Directory?
|Sample MemberClicks Profile ID|
Higher Logic can categorize your Staff differently from your Members. This gives us the ability to add staff to a designated "staff" community, add "staff" ribbons to their profile, and exclude them from the Most Active Members widget. To allow us to do this:
- create a MemberTypeCode in MemberClicks (Oasis) titled Staff,
- assign your team appropriately, and
- note this MemberTypeCode above.
Higher Logic can limit the records being synced to only those records in select Security Groups. If you want to limit the records being synced from your AMS, let your project manager know which of the above Member Types to add to our filter list. Users who are not in these Security Groups will not be able to access the site.
Section III: Expiration date
By default, Higher Logic uses a record's MemberType Expiration Date as the end date to their Community access.
Section IV: Events
The MemberClicks integration does not sync Events to Higher Logic.
Section V: Profile
Member contact information (e.g., name, company address, etc.) is integrated from your AMS to create profiles.
Section VI: Single Sign-On
Single Sign-On (SSO) makes it possible for your members to move between your main organization website and your Community site without having to separately log in to each.
- If you plan to use SSO for your integration, provide "test" Member and Non-Member credentials below.
Additional MemberClicks SSO configuration
To use SSO between MemberClicks and Higher Logic, some additional permissions should be granted to the ClientId provided in Page (1).
- [ClientId] must have access to the /oauth/v1/token endpoint with grant_type = password ("Resource Owner Password Credentials Grant Type")
- For grant_type = authorization ("Authorization Code Grant Type"), access should also be granted and the redirect_uri for [ClientId] should be set to your HL Community site's URL
Additional information is available at https://help.memberclicks.com/hc/en-us/articles/230536267-API-Management.