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, we require access to your API documentation. We request that this information be sent to your project manager.

• You can request this information from your Euclid project manager.
• We cannot proceed with the integration until we have this information.

Provide the following contact information for your Euclid project manager in case we have questions or need additional integration-related information.

Section II: Profile

Member contact information (e.g., name, company address, etc.) is integrated from your AMS to create profiles. By default, the Emp address fields are synced.

Section III: Importing records and granting member status

Higher Logic syncs all records that are flagged as active from your Euclid database into your Community site. Users are placed into Security Groups based upon their Euclid MemberType. Also, all users marked as "IsMember" in Euclid will be added to an "Association Member" Security Group. Staff records must belong to a Staff Member Type. Users will be members of their assigned Security Group.

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

The Euclid Integration does not support an expiration date. Members are expired when they are removed from the Member Type in Euclid.

Section V: Community groups

Community Groups are automatically created based on a user's CommunityGroups data from Euclid.

Section VI: Events

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

A calendar of events is created and available to your members in your Community site.

Section VII: Single Sign-On

Euclid supports Single Sign-On (SSO) with your Community site. This means that users 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.

• If you plan to use SSO for your integration, provide "test" Member and Non-Member credentials below.