Skip to main content

Integrating Glean with PlusPlus

Publish PlusPlus content into your Glean index so people find learning through enterprise search. Covers setup, the daily sync, event display options, and how to tell when indexing has stopped.

Written by Michael Wallace

Your organization uses Glean for enterprise search, and you want PlusPlus content to appear in Glean results so people find learning without starting in PlusPlus.

The integration is one-way. PlusPlus publishes content into your Glean index on a daily schedule. Glean does not send anything back into PlusPlus, and enabling it does not change what anyone sees inside PlusPlus.

Solution

Contact PlusPlus Support before you start. Setup requires a one-time registration step that only Support can run, and the integration indexes nothing until it is done.

In Glean

  1. Add a custom datasource in your Glean instance. Note the name you give it.

  2. Create an API token scoped to that datasource. See Glean's Managing API tokens for the current procedure. Setting an expiry is optional — read When indexing stops below before you do.

In PlusPlus

  1. Go to System Settings > Integrations > Glean.

  2. Turn on Enable Glean integration.

  3. In Glean Datasource, enter the name of the custom datasource you created in Glean.

  4. In Glean API URL, enter your Glean indexing endpoint: https://{SUBDOMAIN}-be.glean.com/api/index/v1
    Include both the -be suffix on the host and the full /api/index/v1 path. PlusPlus uses this value exactly as entered and does not validate it, so a malformed URL saves without complaint and indexes nothing.

  5. In Glean API Token, enter the token you created in Glean.

  6. Optionally configure how events appear — see Event display options below.

  7. Save your changes.
    The panel saves as a whole. Nothing persists until you save.

  8. Tell PlusPlus Support you have saved your configuration. They register the datasource schema in Glean, then run an initial sync.

After Support confirms, your content appears in Glean and refreshes daily.

Go deeper

What gets indexed

The integration indexes articles, Guides, collections, courses, events, Event Series, videos, tracks, and mentorship programs.

Events are indexed only while upcoming. An event drops out of the index once its start time passes, so your Glean results stay focused on sessions people can still attend.

Indexing is all or nothing by type. There are no per-type publishing toggles — you cannot index courses but not videos.

When content appears and disappears

Content syncs once daily, at 13:37 UTC. There is no live update: publishing or editing content in PlusPlus does not push it to Glean immediately, and changes made after a sync wait for the next one. Plan for up to 24 hours between a change in PlusPlus and the same change in Glean.

Removal works the same way, and it works by omission rather than deletion. Each sync uploads the full current set of eligible content, and Glean reconciles away what is no longer present. PlusPlus never issues a delete for an individual item. So archiving, hiding, or deleting content in PlusPlus does not remove it from Glean right away — it stays searchable until the next daily sync.

Turning the integration off stops future syncs but does not clear the index. Because removal happens during a sync, anything indexed before you disabled it stays searchable in Glean. To clear it, remove the datasource on the Glean side.

Controlling who can see indexed content

Glean access to PlusPlus documents is set instance-wide, not per item. PlusPlus does not export per-item permissions, so Glean cannot enforce PlusPlus group membership on individual documents.

Restrict access to indexed documents switches between the two available modes:

  • Off (default): indexed content is searchable by anyone with access to your Glean instance, including people who do not have a PlusPlus account.

  • On: indexed content is searchable only by users Glean recognizes as PlusPlus users. PlusPlus also indexes your active user list so Glean can enforce this.

Changing this setting takes effect at the next daily sync.

The integration is designed to index only content that is public and unrestricted. Because access is instance-wide and cannot be narrowed per item, confirm with PlusPlus Support which of your content is in scope before you enable the integration — particularly if you use restricted channels or group restrictions.

Event display options

Glean has no native concept of an event, so two optional settings make events more legible in search results.

Add dates to Event titles appends the event date to the indexed title, which distinguishes recurring sessions that would otherwise share one name.

Use a template for Events prepends a header to the indexed event description. With it on, enter the header in Template to apply to Events descriptions in Glean. The field accepts any tag valid in event notification templatesdate_time_information and event_location are the common pair — with each tag wrapped in double curly braces. Use Preview to check the rendered header before you save.

Both settings affect only how events appear in Glean. Nothing changes in PlusPlus.

When indexing stops

PlusPlus does not surface indexing failures. There is no status indicator, error banner, or health check in the Glean panel — a configuration with an expired token or a malformed URL looks identical to a working one.

The two most common causes are a Glean API token that has expired or been revoked, and an API URL missing the -be host suffix or the /api/index/v1 path.

If PlusPlus content stops appearing in Glean, or never appeared after setup, contact PlusPlus Support. Failures are recorded in server-side logs that Support can check.

See also

Did this answer your question?