Higher Logic Technical Worksheet:
MemberClicks Integration with the Engagement Platform for Members

Overview:

The technical integration framework between your association management system (AMS) and Higher Logic (HL) will be determined based on the information received in this technical worksheet.  This framework defines how HL will interact with data in your AMS to create member profiles, security groups, communities and events.

After the integration is established, a periodic check for changed records in the AMS (Periodic Refresh) coupled with a comprehensive refresh of each updated record (Member Refresh) yields a robustly integrated ecosystem.  The periodic refresh and member refresh ensure that Higher Logic utilizes the most-up-to-date member data, which in turn leads to increased member engagement, collaboration and retention.

Please fill out the information below in as much detail as possible and contact your project manager should you have any questions.

Section I: Web Service Access

To start the integration, the following access credentials for your AMS must be provided to Higher Logic. Please provide those credentials here.

Database server URL
OrgId
Client Id
Client Secret

 

Section II – Membership Status

Higher Logic will sync all records from MemberClicks (Oasis) to the Online Community.

Please list the member type codes that exist in MemberClicks (Oasis).  For each, please 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
Click here to enter text.	Y/N	Y/N	Click here to enter text.
Click here to enter text.	Y/N	Y/N	Click here to enter text.
Click here to enter text.			Click here to enter text.
Click here to enter text.			Click here to enter text.

Higher Logic can categorize your Staff differently from your Members – this gives us capabilities like adding staff to a designated “staff” community, adding “staff” ribbons to their profile, and excluding them from the Most Active Members widget. To allow us to do this, please create a MemberTypeCode in MemberClicks (Oasis) titled ‘Staff’, assign your team appropriately, and note this MemberTypeCode above.

Higher Logic also has the capability to limit records being synced to only records in certain security groups. If you would like to limit the sync in this way, please let your project manager know which of the above Member Types to add to our filter list. Users that are not in these security groups will not be able to access the site.

Section III: Expiration Date

By default, HL will use a record’s MemberType Expiration Date as the end date to their access to the community.

Section IV: Events

Event information is synced from MemberClicks (Oasis) to the Online Community once per day. A calendar of events will be created and available to Members in the Online Community.

Section V: Profile

Standard member contact information will be integrated from your AMS to create profiles including name, company address, etc.

VII: Single Sign On

Single Sign-On (SSO) allows members to move between your main organizational website and your Connected Community site without having to log in to each separately. Please provide login credentials to a member and non-member, so that we can set up the SSO.

SSO Test Accounts	If you utilize SSO, please provide test credentials:
Member	Username	Click here to enter text.
	Password	Click here to enter text.
Non-Member	Username	Click here to enter text.
	Password	Click here to enter text.

Additional MemberClicks SSO Configuration

To effect Single Sign-On (SSO) between MemberClicks and Higher Logic, some additional permissions should be granted to the ClientId provided in Page (1).

1. Basic Authentication:

[ClientId] needs access to the /oauth/v1/token endpoint with grant_type = password

2. Single Sign On:

For grant_type = authorization, access should also be granted and the redirect_uri for [ClientId] should be set to the HL Community Site URL

Additional MemberClicks SSO Configuration

To effect Single Sign-On (SSO) between MemberClicks and Higher Logic, some additional permissions should be granted to the ClientId provided in Page (1).

1. Basic Authentication:

[ClientId] needs access to the /oauth/v1/token endpoint with grant_type = password (“Resource Owner Password Credentials Grant Type”)

2. Single Sign On:

For grant_type = authorization (“Authorization Code Grant Type”), access should also be granted and the redirect_uri for [ClientId] should be set to the HL Community Site URL

** Additional Information can be found here: https://help.memberclicks.com/hc/en-us/articles/230536267-API-Management **