> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dovetail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Dovetail with Glean

Many organizations use **Glean** to search across their internal knowledge base and tool stack. You can make your **Dovetail data and docs discoverable in Glean** by indexing Dovetail content into your Glean tenant.

This guide explains how the two systems work together and what your team needs to set it up.

## What this integration provides

When connected, you can:

* Search across Dovetail docs directly from Glean
* Use Glean Chat to answer questions using your research data
* Distribute customer insights to Sales, CS, Product, and Support teams
* Keep permissions intact so users only see what they should

## How it works

Dovetail acts as a **source of data**, and Glean acts as a **search and distribution layer**.

To connect them, your engineering team sets up a **custom connector** that:

1. Fetches content from Dovetail (via API or export)
2. Pushes that content into Glean using Glean’s **Indexing API**
3. Syncs on a schedule to keep content up-to-date

Once indexed, Dovetail content becomes part of Glean’s search and chat experience.

## Technical requirements

To set up this connection, you’ll need:

### 1. Access & credentials

* **Dovetail** admin access (to fetch doc content)
* **Glean** admin access (to configure a custom connector)
* A **Glean Indexing API** token for pushing content
* **Dovetail API token** if you’re using the API for extraction

### 2. Engineering resources

Your team should be comfortable with:

* Calling REST APIs
* Handling auth tokens
* Running scheduled sync jobs or webhooks
* Mapping access permissions for users

Languages commonly used: Node.js, Python, Go — take your pick.

### 3. Hosting for the connector

You’ll need somewhere to run the sync job — e.g.:

* AWS Lambda
* Google Cloud Functions
* Azure Functions
* Any container/VM

## Data types you can index

You can index and [reference in Dovetail’s API](https://developers.dovetail.com/reference/get_v1-token-info). Most teams index:

* Docs
* Tags
* Highlights
* Projects
* Channels
* Contacts

## Permissions & access control

To keep information secure, the connector should:

* Assign **document-level permissions** based on Dovetail access
* Match users by **email** or **SSO identity**
* Update permissions during each sync

## Syncing & freshness

Most organizations sync:

* **Daily** for general research
* **Hourly** for active research cycles
* **On-change** if using Dovetail webhook events

You can choose what makes sense for your workflow.

## What your engineering team builds

Your connector will need to:

1. **Fetch** content from Dovetail (API/export/database)
2. **Transform** objects into Glean’s indexing format
3. **Push** documents via Glean’s Indexing API
4. **Handle** permissions
5. **Schedule** recurring syncs

Once deployed, it becomes a “set and forget” pipeline.

## Limitations to be aware of

* There is currently **no native 1-click integration**
* Requires **engineering support** to set up
* Content freshness depends on your sync interval