Highspot

The Highspot connector enables you to index and search content from Highspot directly within Glean. By integrating Highspot, you can quickly find Spots, items, and associated metadata, streamlining access to critical sales and marketing assets. The connector fetches content that the API user has access to, including all Spots and all Items within those Spots, along with their metadata and content.

Supported features and limitations

The Highspot connector is designed to ingest and index content from Highspot, making it searchable within Glean. This section outlines the supported objects, API endpoints, limitations, crawling strategy, and how results are displayed.

Supported objects and entities

Object/Entity	Description
Spots	All Spots accessible to the API user
Items	All Items within accessible Spots. For items, Glean crawls content and metadata.

Supported API endpoints and features

• /users: Fetches users from Highspot.
• /spots: Fetches Spots. In content crawl, this endpoint can be used to retrieve all spots across the tenant. Optionally, results can be scoped per user by using impersonation to apply that user’s permissions.
• /items/%s: Lists items within a Spot, including metadata.
• /items/%s/content: Downloads the content of a given item.

Page size is generally set to 100.

Limitations

• The connector requires a paid Highspot license that supports API access.
• There is currently no direct API to list all users with access to a given Spot, and user impersonation is used as a workaround.
• Due to API limitations, Glean cannot mirror Highspot’s native permissions. All Highspot documents indexed by Glean are visible to all Highspot users in Glean.

Crawling strategy

Crawl Type	Full Crawl	Incremental Crawl	People Data	Activity	Update Rate	Webhook	Notes
Spots & Items	Yes	No	No	No	4 hours	No	Frequency depends on object type and impersonation used for permissions.
Users	Yes	No	Yes	No	1 hour	No	Users fetched for permission mapping.

The default frequency for content crawl is 4 hours and for identity crawl it is 1 hour.

Results display

Highspot results appear in Glean search with associated metadata such as title, author, date of publishing, and last modification date.

Requirements

To use the Highspot connector, you must meet certain technical, credential, and permission requirements, as well as perform some preliminary setup in Highspot.

Technical requirements

• You must have a Highspot instance with API access enabled.
• Glean must be deployed in your environment with access to the Glean admin console.
• All data is stored in your GCP project and no data leaves your environment.

Credential requirements

• API credentials like the client key and client secret are required. These are provided by Highspot after API access is enabled for your instance.
• A dedicated API user is created in Highspot for integration purposes.

Permission requirements

• The API user’s access in Highspot determines what content is crawled and indexed.
• For full identity-based permissions support, you must enable Impersonation in Highspot REST API.

Preliminary setup

• Contact Highspot to enable API access for your organization.
• Obtain the necessary API credentials like the client key and secret.
• (Optional) Enable impersonation in the Highspot API for enriched permissions and identity crawling.

Configuration and setup instructions

This section guides you through configuring and setting up the Highspot connector in Glean. Most setup steps are performed in the Glean admin console.

Prerequisites

• Highspot instance with API access enabled.
• API credentials (client key and secret) from Highspot.
• (Optional) Impersonation enabled in Highspot API for advanced permission support.

Enable API functionality

Glean requires API functionality to search Highspot content. Contact the Highspot support team to enable API functionality for your instance and share the credentials with Glean.

Determine the subdomain of your Highspot instance

You can determine the subdomain of your Highspot instance by checking the URL you use to access the instance. For example, if you access Highspot at acme.highspot.com, the subdomain is acme.

Determine client information

For Glean to access your Highspot instance API, provide the API URL, API client key, and API client secret.

To get the API URL, client key, and client secret:

1. Sign in to Highspot. Open your User Profile in the top-right corner and navigate to Settings.
2. In the left navigation bar, under Developer, select Basic.
3. Copy the API URL and enter it in the API URL field in the Glean Highspot connector. Example format: https://api.highspot.com/v0.5.
4. Under API Credentials, click Generate API Key and Secret.
5. Copy Key and enter it in the API client key field in Glean.
6. Copy Secret and enter it in the API client secret field in Glean.

Connect Highspot and Glean

To validate the credentials and connect the Highspot connector to Glean:

1. In the Glean Admin console, navigate to Data sources.
2. Click Add data source and add a new Highspot connector.
3. Enter the required information:
   • Highspot subdomain
   • API URL (for example, https://api-su2.highspot.com/v1.0)
   • API client key
   • API client secret
4. Click Save.

Crawl configuration options

• You can control which Spots or items are indexed by modifying the API user’s access in Highspot.
• There are no explicit red/greenlist or lookback period options; access is managed through the API user’s permissions.
• The connector runs scheduled full crawls (not incremental crawls for Spots, items, or users). Typical update rates are between 1 and 4 hours depending on the object type.

Permissions & security

Data and Metadata Ingested:

• Spots, items, item metadata, and item content accessible to the API user.

Permission propagation logic:
Due to Highspot API limitations, when installed in its default configuration, all indexed Highspot content is visible to all Highspot users in Glean. An optional toggle enables spot-level permissions, which relies on user impersonation to fetch each user’s Spots and map content visibility to their spot membership. Enabling the spot-level permissions toggle requires a Highspot admin to authorize user impersonation. This toggle is off by default.

Security & compliance notes:

• Authentication is handled through API credentials (client key and secret).
• All data remains within your GCP project and no data leaves your environment.

Data privacy implications:

• The connector may impact your organization’s data privacy posture, as all indexed Highspot content becomes visible to all Highspot users in Glean, regardless of original Highspot permissions.

For any issues or concerns, contact the Glean support team.