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, you must provide Fonteva Service login credentials to Higher Logic. To obtain Fonteva Service login credentials, contact your Fonteva administrator and inform them of your integration with Higher Logic.

• Your Fonteva administrator will provide you with a Fonteva Service username and password to your production database for the integration.
• These credentials should have a profile set to System Administrator.
• Provide these credentials in the table that follows.

As this record will be used for programmatic access via the API, it should not have a periodic password-reset requirement, which would result in complete outages in the integration.

NOTE: If you are creating a user, specify a Username that identifies <your org>, such as integrationhl@<yourorg.com>.

Whether creating a user or using an existing one, set the contact Email Address to integration@higherlogic.com.

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

If you have checkbox fields which indicate that a contact should be synced to or excluded from Higher Logic, or excluded from email communication pursuant to GDPR regulations, note them below.

Security Groups

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 Security Groups 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 Fonteva Integration does not support an expiration date. Members are expired when they are removed from the corresponding Security Group object in Fonteva.

OrderApi__Expired_Date__c for badges

OrderApi__Current_Term_End_Date__c for subscriptions

Section V: Community groups

Community Groups are automatically created based on Fonteva's standard object outlined below.

• Check all that apply.

Section VI: Events

Event information is synced from Fonteva 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

Fonteva 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 SSO testing credentials if you plan to use SSO for this integration.

• Provide your project manager with the SAML Metadata with the custom attribute named ContactId with the value CASESAFEID($User.ContactId).