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

# Push Knowledge Base Articles to IT Glue

> Sync Thread Client Intelligence knowledge base articles into a dedicated Thread Knowledge Base folder inside each mapped IT Glue organization.

<Warning>
  **Beta.** The IT Glue KB push is in limited beta. It is off for all workspaces by default and is enabled per workspace by Thread. Reach out to your Thread CSM if you want it turned on.
</Warning>

## What it does

The IT Glue KB push writes your **Thread Client Intelligence knowledge base articles** back into IT Glue, so the documentation your team maintains in Thread also lives alongside the rest of your IT Glue content.

For each enabled client, Thread:

* Creates a dedicated **Thread Knowledge Base** folder inside that client's mapped IT Glue organization.
* Creates a document in that folder for each Thread KB article on the client.
* Keeps the documents in sync as articles change in Thread.

This is the opposite direction from the [IT Glue → Super Magic sync](/integrations/it-glue-super-magic), which reads from IT Glue into Thread. The KB push writes from Thread into IT Glue.

## What gets touched (and what doesn't)

The integration is intentionally narrow. It only ever touches documents it created itself.

* **Scope:** the dedicated `Thread Knowledge Base` folder inside each mapped IT Glue organization. Nothing outside that folder is read or written.
* **Tracking:** every KB article Thread pushes is tracked with a Thread KB article → IT Glue document mapping plus a content hash.
* **Unchanged articles** are skipped — no API call, no update.
* **Changed articles** are replaced (delete + recreate) so the IT Glue document matches the current Thread article.
* **New articles** get a new document created in the folder.
* **Pre-existing, native IT Glue articles** outside the Thread Knowledge Base folder are never read, updated, or overwritten. There is no path by which this feature can modify your existing IT Glue documentation.

## Requirements

Before enabling the push for a client, confirm:

* The [IT Glue integration](/integrations/it-glue-super-magic) is connected for the workspace.
* Each Thread client you want pushed is mapped to an IT Glue organization (same mapping used by the Super Magic sync).
* The IT Glue API key has **write** access to documents in the mapped organizations. The read-only key used for the Super Magic sync is **not** sufficient on its own for the push direction.
* Client Intelligence knowledge base articles exist on the client you want synced.

Turning the push off for a client stops future pushes. Documents already created in IT Glue are not deleted.

## Current limitations

* No per-article opt-out or folder-level exclusion controls yet — every KB article on an enabled client is pushed.
* Changed articles are handled as delete + recreate, so the IT Glue document ID for a given article can change across syncs.
* Enablement and monitoring are handled by Thread today; there is no self-serve in-product control yet.

## Questions?

Reach out to your Thread CSM or email [help@getthread.com](mailto:help@getthread.com).

<Note>
  See **Integrations** updates in the [changelog](/changelog/q3-2026).
</Note>


## Related topics

- [Getting Started with Client Intelligence](/ai-agents/getting-started-with-knowledge.md)
- [Magic Recap Template Library](/assistive-ai/magic-recap-template-library.md)
- [Knowledge Base Taxonomy](/skill-library/documentation/knowledge-base-taxonomy.md)
