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 Spots and 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	By default, only official Spots accessible to the API user are indexed. Glean can optionally be configured to index all accessible Spots, including unofficial and personal Spots.
Items	Items within indexed Spots. Glean crawls content and metadata for each item. Item visibility follows the parent Spot's access.

Supported API endpoints and features

• /users: Fetches users from Highspot.
• /spots: Fetches Spots for content indexing. When spot-level permissions are enabled, Glean also uses this endpoint with impersonation to fetch each user’s Spots and build access mappings.
• /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 no direct Highspot API to list all users with access to a given Spot. When spot-level permissions are enabled, Glean uses user impersonation to determine each user’s Spot membership.
• By default, only official Spots are indexed. To index all accessible Spots, including unofficial and personal Spots, contact Glean support.

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.
• To enforce spot-level permissions in Glean, you must enable Impersonation in Highspot REST API for the API client used by Glean.

Preliminary setup

• Contact Highspot to enable API access for your organization.
• Obtain the necessary API credentials like the client key and secret.
• To enable spot-level permissions, enable impersonation in the Highspot API for the API client used by Glean. Then contact Glean support to turn on spot-level permissions for your connector.

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.
• To enforce spot-level permissions, enable impersonation in the Highspot API for the API client used by Glean.

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. By default, only official Spots are indexed. To include unofficial and personal Spots, contact Glean support.
• There are no explicit allowlist/denylist 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.

Default mode: In the default configuration, all indexed Highspot content is visible to all Highspot users in Glean. Spot-level permissions aren’t enforced until you complete additional setup.

Spot-level permissions (optional): Glean supports spot-level permission enforcement for Highspot. When enabled, users only see Spots and Items they’re authorized to access. Item visibility follows the parent Spot’s membership.

To enable spot-level permissions:

1. In Highspot, enable Impersonation in Highspot REST API for the specific API client used by Glean.
2. Contact Glean support to enable spot-level permissions for your connector.
3. After Glean enables the setting, a new identity crawl runs to map each user’s Spot membership.

warning

Impersonation must be enabled for the API client that Glean uses. If impersonation isn’t configured for the correct client, the identity crawl can fail with 401 Unauthorized errors, and content may not appear correctly in search results.

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.

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