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: Web service access

To start the integration, Higher Logic will provide a set of stored views and procedures that are to be installed in your Personify instance by your Personify admin. These stored views and procedures are used to generate data for contacts and their associated data in your Community site.

After the views and stored procedures have been installed, provide Higher Logic with Personify Data Services API credentials with the following permissions.

• SSOCustomerTokenIsValid
• SSOCustomerGetByEmail
• SSOCustomerGetByCustomerToken
• CustomerAuthenticateAndGetId
• VendorTokenEncrypt
• CustomerTokenDecrypt
• TIMSSCustomerIdentifierGet

After the stored views and procedures are installed and Personify Web Services API credentials the integration of contact data can proceed.

Section II: Profile

Member contact information (e.g., name, company address, etc.) is integrated from your AMS to create profiles.

Section III: Importing records and granting member status

The default logic provided extracts all the membership products within Personify. Each user order to a membership product will be converted to a Security Group membership that will be populated in Higher Logic under the MBR_ORDER type.

• Security Groups are automatically created based on a user's MemberType.
• Staff records must belong to a Staff Member Types.

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 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 IV: Expiration date

Higher Logic leverages the membership end date in Personify to expire members.

Section V: Community groups

Higher Logic syncs Personify committees using COM_COMMITTEE_MEMBER and CUSTOMER for committee memberships and information.

Section VI: Events

Event information is synced from Personify to your Community site once per day.

A calendar of events, based on Personify Event Products, is created and available to your members in your Community site.

Section VII: Single Sign-On

Personify supports Single Sign-On (SSO) with your Community site. This means that your members will be able to move between your main organization website and your Community site without having to separately log in to each.

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.

Provide the following test credentials to Higher Logic if you plan to use SSO for this integration.