This Services Description sets forth certain implementation services provided by Higher Logic referenced on the Order Form and described below (the “Implementation”). The Order Form and Services Description are subject to and governed by the Master Subscription Agreement as entered into by the parties and referenced in the Subscriber’s Order Form (the “Master Subscription Agreement”).
By executing the Order Form to which this Services Description is attached, Subscriber hereby expressly agrees to all terms and conditions of the Order Form, this Services Description and the Master Subscription Agreement. Defined terms shall have the meaning accorded to such terms in the Master Subscription Agreement unless otherwise set forth herein. In the event of any conflicts in terms among the Order Form, this Services Description and the Master Subscription Agreement, the terms of the Master Subscription Agreement shall prevail.
Higher Logic will provide the Implementation services related to the Subscriber’s Higher Logic Community Plus for Customers package (the “Higher Logic Community Plus for Customers” or “Plus Package”) as set forth below.
Plus Package core platform functionality includes:
The Implementation will consist of the activities set forth below in the Schedule & Milestones section. For the avoidance of doubt, the Implementation will begin upon Subscriber’s execution of the Order Form which references the Implementation and upon Subscriber’s confirmation of readiness to start the Implementation (if date is later than the execution of the Order Form). The first step in the Implementation is a community launch questionnaire (the “Community Launch Questionnaire”) designed to outline and confirm the goals, objectives, milestones, schedule and next steps required to start the Implementation including key information which is required as part of the site provisioning process. The discovery process is to be completed by the Subscriber within two (2) business days of the execution of the Order Form to which this Services Description is attached.
Higher Logic will designate a point of contact to serve as an onboarding liaison, helping guide and facilitate the Subscriber through various tasks associated with site and integration configuration. Subscriber will designate a point of contact (administrator) to perform the various tasks in support of the onboarding and integration setup and lead the Subscriber’s Implementation tasks through the Implementation lifecycle.
The Implementation lifecycle is defined by three primary phases:
Phase I is the onboarding and site configuration period designed to rapidly provide a working site environment for the Subscriber. The Subscriber plans the site by completing the Community Launch Questionnaire and Higher Logic builds the site per Subscriber’s information provided.
Phase II is focused on education & training in which the Subscriber will be provided a defined curriculum through on-demand training designed to mirror the capabilities and defined functions of the Plus Package. This phase is to be supported by the Subscriber’s resources and support the Subscriber’s desired Implementation timeline. During this phase the Subscriber will be provided access to a support/onboarding community within the Higher Logic User Group (HUG). The HUG will be used by the Subscriber for access to support and other Higher Logic resources.
Phase III is for readiness and go-live preparation.
Subscriber’s instance of the Plus Package will be delivered within one (1) to two (2) weeks of receipt of the completed Community Launch Questionnaire. The timeline for populating user records on to the site is at the discretion of the Subscriber. The supported record creation methods and estimated timelines are described below in the section: User Record Creation and Supported Integrations.
The below schedule and milestones note the core elements of a Plus Package project.
All timelines are subject to customer completion of requested information in deliverables.
| Milestone | Estimated Timeframe/Medium
(all timeframes relative to execution of Order Form unless otherwise noted) |
|---|---|
| Execution of order form referencing this implementation | Date of execution of the Order Form |
| Subscriber completes Community Launch Questionnaire and Technical Worksheet (if applicable) | Within 2 business days |
| Site Provision & Initial Contact Load | Within 4 business days |
| Data Validation | Within 5 business days |
| Subscriber completes DNS updates | Within 5 business days |
| Training – Subscriber completes self-paced training | Within 7 business days |
| Final pre-launch site review – Subscriber completes launch checklist | Within 8 business days |
| Go live | Timeline determined by Subscriber. Within 3 business days of final pre-launch checklist or within 11 business days of execution of the Order Form (recommended) |
| Launch Advocacy Module – Subscriber completes self-paced Advocacy module training and launches program. | Within 1 week of Go live (recommended) |
| Post launch review and transition report | Within 1 month of go-live |
Project Owner: Subscriber will assign a single point of contact (“POC”) to function as Subscriber’s project coordinator/administrator and will serve as the primary channel of communication throughout the Implementation. POC will work directly with the Higher Logic team to coordinate the internal efforts of the Subscriber’s stakeholders and departments. Resource Commitment During Implementation: Approximately 6 – 8 hours per week throughout the duration of Implementation.
User Stakeholder(s): The person(s) who is the primary decision maker regarding who has access to the site, what content users are consuming, and how it benefits the users. They may determine community security and have the responsibility to execute the administrative community management tasks associated with managing the site. Resource Commitment During Implementation: 8–10 hours consisting of engagement strategy calls, and on-demand training.
IT and Data Stakeholders: Owners of contact data and account creation in Higher Logic from the database of record. This may be a database administrator who works to provide a user list or any other database extracts to help add and configure data in Higher Logic. Depending on the requirements they may also be involved with SSL and DNS configuration. Resource Commitment During Implementation: 8-10 hours depending on technical requirements.
Higher Logic offers five mutually exclusive methods for user record creation and contact detail updates. Subscriber will select one of the following methods:
a. Standalone “local” account creation and management
b. Upload via spreadsheet
c. Standard Salesforce (SFDC) Integration with Salesforce Contact Manager
e. API/Subscriber-managed integration (Push API integration)
Standalone “local” account creation and management method:
The Standalone account creation method allows for the Subscriber’s Users and User authentication to be managed directly in the Plus Package. With this method, the Plus Package serves as a member portal for users to allow for creation of accounts, updates to profiles, and login/authentication.
Subscriber is responsible for managing user records based on Higher Logic’s documentation.
Important Note: Single Sign On (SSO) is not supported with this method, as Higher Logic is not an Identity provider (IDP) for external systems.
This user creation method is the fastest to set up and maintain, allowing for a one-time upload, then local account registration and updates moving forward.
Timeline: One (1) business day from data provided by Subscriber for upload.
Upload via Spreadsheet method:
The Upload via spreadsheet method allows for Subscriber super admins to import, manage, and update contact records directly in the platform via spreadsheet. With this method, the spreadsheet serves as the database/single source for record creation and updates. All record creation, along with contact record updates, is managed solely through the spreadsheet.
Considerations for the upload:
The Upload method is considered a moderate effort level.
Timeline: Two (2) business days to one (1) week depending on the need for SSO.
Standard Salesforce (SFDC) Integration Method with Contact Manager:
The standard Salesforce Integration to the Plus Package allows for specified contact and security group data to sync from Subscriber’s existing production Salesforce instance to the Plus Package.
The Subscriber acknowledges and agrees that the following prerequisites have been confirmed and satisfied by the Subscriber prior to integration:
(Optional) Salesforce Contact Manager: If using the Standard Salesforce integration method, the Subscriber may leverage Higher Logic’s Salesforce Contact Manager. This feature allows the creation and updates to Salesforce contact records through a standard form in the Plus Package. Salesforce Contact Manager supports the following actions:
The effort level to establish the Salesforce user creation method is considered moderate to high with Higher Logic’s contact manager and SSO.
Timeline: The Standard Salesforce integration timeline is one (1) week for initial record import.
Other Standard Integrations:
Higher Logic offers other standard integrations that are available and listed at the following support site: https://support.higherlogic.com/hc/en-us/articles/360058183111
API/Subscriber–managed integration (Push API integration method):
This integration method allows the Subscriber to manage and integrate user record creation, updates, and removal/deactivation of accounts via PUSH API endpoint provided by Higher Logic. In this method, the Subscriber is in full control of the integration frequency and is responsible for any development and workflow necessary to perform and maintain the integration.
The Subscriber acknowledges and agrees that the following prerequisites have been confirmed and satisfied by the Subscriber prior to integration:
The Push API user creation method is considered most advanced as it requires the Subscriber or Subscriber’s vendor to develop, test and maintain the integration, user registration, and associated workflows to establish the integration.
Timeline: The Push API timeline is driven by the Subscriber’s IT team/ third-party vendor.
Higher Logic supports standard SAML 2.0 for upload and integrated Subscribers. Subscriber acknowledges and agrees that the following prerequisites – which are necessary to support SSO – have been confirmed and satisfied by Subscriber prior to the integration: Subscriber’s SSO is compatible with Higher Logic’s SSO (SAML 2.0)
Please click the link for details associated with the SSO option.
All sites will be provisioned on the standard Higher Logic link convention of “subscriber”.connectedcommunity.org. Higher Logic allows the community site to have a defined primary subdomain within the Subscriber’s Domain Name Service (DNS) at the discretion of the Subscriber. Higher Logic will provide the Subscriber with best practices and assistance in establishing an appropriate subdomain for the Community, if desired. Subscriber is solely responsible for all DNS configurations and maintenance, and ensures that domains are registered to the Subscriber as a third-level existing Subscriber-owned web domain (ex. community.subscriber.com). Higher Logic is not a domain registrar and is not responsible for managing Subscriber domain names.
Higher Logic will apply an SSL certificate free of charge upon DNS subdomain configuration via LetsEncrypt Service. This certificate will be managed by Higher Logic and will automatically remain current.
Higher Logic will configure email notifications to send all outgoing emails with a Higher Logic owned or controlled domain name in the envelope/mail-from domain email headers. Higher Logic will adhere to GDPR compliance standards and integrate opt out status information. Mail published from Higher Logic’s Online Community platform will be published from the connectedcommunity.org domain.
Testing: Education resources for beta testing scenarios and actions are available in the Community Plus for Customers learning path here: https://academy.higherlogic.com/paths. Higher Logic will review and prioritize product configuration change request identified during testing. Higher Logic will work with the Subscriber’s IT Project Manager to verify criticality and assign their own – and the Subscriber – resources to resolve the items.
Launch Readiness: The final Go-Live decision will be made solely by the Subscriber.
Post-Launch Support: The Higher Logic PM will remain on the project for no more than 30 days after the go-live date. Following the Go-Live, the PM will conduct the Post Launch Review and Transition Session to review current activity and close out remaining issues. Following Post Launch Review and Transition, which marks the end of the Implementation phase, Subscribers are granted access to Higher Logic’s Online Support Portal and have full access to a ticketing system and escalation paths.
Testing: The Higher Logic PM will provide HUG resources to beta testing scenarios and actions for beta users. Higher Logic will review and prioritize product configuration change request identified during testing. Higher Logic will work with the Subscriber’s IT Project Manager to verify criticality and assign their own – and the Subscriber – resources to resolve the items.
Launch Readiness: The final Go-Live decision will be made solely by the Subscriber.
Post-Launch Support: The Higher Logic PM will remain on the project for no more than 30 days after the go-live date. Following the Go-Live, the PM will conduct the Post Launch Review and Transition Session to review current activity and close out remaining issues. Following Post Launch Review and Transition, which marks the end of the Implementation phase, Subscribers are granted access to Higher Logic’s Online Support Portal and have full access to a ticketing system and escalation paths.
Higher Logic reserves the right to reassign resources, reschedule and/or re-prioritize the Implementation or any milestone related to the Implementation in the event that Subscriber is not responsive and/or in the event that the Subscriber requests a delay of the Implementation.
The parties acknowledge and agree that the activities listed below are outside the scope of this Implementation and are not provided by Higher Logic as part of the Implementation. In the event that Subscriber requests an out-of-scope service, whether included on this list or otherwise determined by Higher Logic to be out of scope (a “Change Request”), Higher Logic will consider such a request and may, in its sole discretion, provide the services for an additional time and materials (T&M) fee of $200 per hour. In the event of such a Change Request, Higher Logic will prepare a cost estimate and timeline for the additional services and, upon Subscriber’s execution of an order form detailing the Change Request Services, will commence work. Higher Logic reserves the right to decline any change request in its sole discretion.
Examples of items which are considered out-of-scope for this Implementation include:
Payments as set forth in the Order Form.