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
• events.

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: Basic info

This section should be completed by the Higher Logic project manager.

Section II: Web service access

To start the integration, provide MemberSuite (MS) credentials to Higher Logic by completing the fields in the following table.

If you have trouble finding this information, consult MemberSuite Support.

Section III: Profile

Member contact information (e.g., name, company address, etc.) is integrated from your AMS to create profiles. This information comes from fields on the Individual record in MemberSuite.

Section IV: Importing records and granting member status

During the sync, Higher Logic uses data that is retrieved from MemberSuite to create Security Groups in your Community site; these are usually based on Member Types.

• Security Groups make it possible for site administrators to restrict access to pages and/or communities to subsets of users.
• Security Groups also grant member status in your Community site. Those that do are grouped into a larger Security Group called IsMember, which administrators can use to easily restrict access to all members at large.

Higher Logic will integrate (as Security Groups) all Member Types in MemberSuite where "ReceivesMemberBenefits" is true.

• By default, Higher Logic will use a record's Membership.ExpirationDate as the end date to their Security Group membership.
• In most cases, the user will no longer have access to your Community site when their end date is reached.

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 Membership Type in MemberSuite titled Staff,
• assign your team appropriately, and
• note this Membership Type Code 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 V: Communities, Chapters, and Events

Committees and Chapters designated in MemberSuite will be created and populated in your Community site in the form of hidden committees and hidden chapters, respectively.

Members will be populated into these committees and chapters based on their designations in MemberSuite. No notifications or alerts of community/chapter inclusion will be sent to members until these objects are made visible and email subscriptions for members are updated.

Section VI: Single Sign-On and test login credentials

In order to set up SSO, you must provide Higher Logic with Portal login credentials to use for testing. These credentials are separate from web service access information and can be any member.

NOTE: Are you planning an SSO implementation with Higher Logic? If so, your implementation project may require a one-time fee for configuration and testing. Reach out to us to learn more.

Ensure these have been tested on your MS Login Form URL (see Section II).