Skip to main content

Service ownership, on-call, and docs live in a portal nobody can search, and the knowledge about those services lives everywhere else. This recipe turns a lightweight service-catalog portal into the one-stop shop: its catalog becomes searchable in Glean, and Glean's permission-aware search and chat come back into the portal itself.

Service catalogYAML + runbooks
Custom connectorIndexing API
Gleanpermission-aware index
Portal UIWeb SDK embed
A Glean instance where you can add a custom datasource
A Glean-issued Indexing API token
Node.js 18+ to run the portal app locally
Take it further
  • Add an on-call answer card to the portal backed by a Client API search call.
  • Extend the connector with incremental sync and identity mapping so catalog permissions mirror your org.
  • Wire the portal's "ask" box to open Glean Chat with the current service as context.

How do I find out who is on call?

Returns a non-empty answer with at least one citation carrying a real title and URL from your indexed engineering content.

How do I deploy a service?

Returns a non-empty answer with at least one citation carrying a real title and URL, drawn from your own indexed content.

What's our incident response process?

Returns a non-empty answer with at least one citation carrying a real title and URL, drawn from your own indexed content.

Each of these was run against a live Glean instance on 2026-08-02.

Paste into Claude Code, Cursor, or Codex.

At a glance
SurfacesConnector SDK, Indexing API, Web SDK, Client API
StatusShowcase
Time~30 min