NOTE: This Higher Logic Technical Worksheet is intended for customers with Engagement Platform for Members.

The technical integration framework between your Customer Relationship Management (CRM) database 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 CRM to create:

• member profiles,
• security groups,
• communities, and
• events.

After the integration is established, a periodic check (Periodic Refresh) for changed records in your CRM, 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.

Section I: Web service access

To start the integration, provide Salesforce Service login credentials to Higher Logic. To obtain Salesforce Service login credentials, contact your Salesforce administrator and inform them of your integration with Higher Logic.

• Your Salesforce administrator will provide you with a Salesforce 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 below.

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

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

Provide the name of the field on the contact record that determines if an account is active. Higher Logic will use that field to determine which records are synced to your Community site.

NOTE: In accordance with GDPR regulations, the Email Opt Out flag for users on Higher Logic will be integrated with the HasOptedOutOfEmail checkbox field on the Contacts in Salesforce.

Section III: Communities and Security Groups

In order to pull fields from Salesforce into your Community site as Security Groups, custom fields have to be set up on the Contacts in your Salesforce environment depending on the data that is needed to create community groups. Prepend the names of these custom fields with HL_ so that they are clearly defined as fields that should be integrated.

• For example, HL_Security_Group_Field

Salesforce documentation

To learn about creating custom fields in Salesforce, see Create Custom Fields.

To learn about creating workflow rules in Salesforce, see Create a Workflow Rule. You can use these to systematically populate custom fields based on user-defined criteria.

Security Groups

Higher Logic syncs all active records from your Salesforce database into your Community site based on the information provided in this worksheet.

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 CRM, let your project manager know which field values to add to our filter list. Users who are not in these Security Groups will not be able to access the site.

Communities

Communities are created locally via the Higher Logic user interface. As new groups are created, administrators can add and invite users, or users can opt in, depending on your preferred privacy settings.