To install the Higher Logic web service, we need remote access to your web server.
|iMIS Webservice URL|
Section I: Importing records and granting member status
- Higher Logic will import Member Types with a status of A
- Customers create a Staff Member Type
- By default, Higher Logic will use a record's Paid_Thru as the end date to their Security Group memberships.
- Higher Logic will import the Exclude Directory
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, 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 II: Community groups
Higher Logic will create a community group for Chapters, Committees, and Events as Hidden Communities. Use the checkboxes to indicate what to sync.
- Committees are pulled from X
- Chapters are pulled from X
- Events are pulled from X
|Sync Committees?||☐||Based on Activity.Other_Code where Activity.Activity_Type = 'COMMITTEE'
Start Date = Activity.Effective_Date (if applicable)
End Date = Activity.Thru_Date (if applicable)
Role = Committee_Position.Title (if applicable)
|Sync Chapters?||☐||Based on Name.Chapter and Product.Product_Minor where Product.Product_Major = 'CHAPT'
End Date = Name.Paid_Thru (if applicable)
|Sync Events?||☐||Based on Activity.Product_Code and Meet_Master.Meeting where Activity.Activity_Type = 'MEETING', as well as Orders.Order_Number and Order_Meet.Meeting where Orders.Stage <> 'CANCELED'|
Section III: Events
Events can be synced and displayed in the calendar of events on your Higher Logic Community site.
Section IV: Profile
Member contact information (e.g., name, company, address, etc.) is synced from iMIS to create profiles in your Higher Logic Community site.
Section V: Single Sign-On
Provide a username, password, and member ID of a user (preferably a test record) who is allowed to log in to your Higher Logic Community site.