> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Business Knowledge

Canonical URL: https://posthog.com/docs/business-knowledge

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Where you can use it](#where-you-can-use-it)
- [Where knowledge comes from](#where-knowledge-comes-from)
- [Use cases](#use-cases)

**Private beta**

Business Knowledge is in private beta. If **Business Knowledge** isn't in your PostHog sidebar, your project isn't in the beta yet. [Send feedback in the app](https://app.posthog.com/#panel=support%3Afeedback%3A%3Alow%3Atrue).

Business Knowledge stores the facts PostHog uses when it answers questions about your business. PostHog AI, Support, and the Business Knowledge MCP tools all read the same sources.

[Get started](https://posthog.com/docs/business-knowledge/start.md)

## Where you can use it

Add sources in PostHog. PostHog AI, Support, and MCP then read those same sources.

PostHog Web

Add a text source, a public page, or a file, then ask in the Playground what's covered and what's missing.

[Add a source →](https://posthog.com/docs/business-knowledge/start.md)

PostHog AI

PostHog AI searches these sources when a question is about your product, policies, or team.

[Ask PostHog AI →](https://posthog.com/docs/posthog-ai.md)

Support

Support reads the same sources when it drafts a reply.

[Learn from support →](https://posthog.com/docs/business-knowledge/learn-from-support.md)

MCP

Search sources, read the surrounding text, and add or update a source. The tools need the `business_knowledge:read` or `business_knowledge:write` scope.

[MCP tools reference →](https://posthog.com/docs/model-context-protocol/tools.md)

## Where knowledge comes from

| Source | What you add | Guide |
| --- | --- | --- |
| Text | A policy, an FAQ, or any other text you paste | [Text](https://posthog.com/docs/business-knowledge/sources.md#text) |
| URL | A public page, a sitemap, or a crawl of one site | [URL](https://posthog.com/docs/business-knowledge/sources.md#url) |
| File | A PDF, DOCX, Markdown, CSV, or plain text file | [File](https://posthog.com/docs/business-knowledge/sources.md#file) |
| Learned | Reusable answers from resolved support tickets | [Learn from support](https://posthog.com/docs/business-knowledge/learn-from-support.md) |
| GitHub | Selected repositories. File names and the README are searched, then a file is read. The code isn't indexed. | [GitHub repositories](https://posthog.com/docs/business-knowledge/github.md) |

## Use cases

-   A customer asks for your refund rules. The reply comes from the refund policy you pasted or from the page you indexed.
-   Someone asks PostHog AI which plan includes a limit. The answer comes from your pricing page.
-   Every reply should follow the same tone. Turn on **Always include in replies** for that source.
-   Your docs site changes. A URL source on a daily refresh picks up the new pages.
-   A human resolved the same support question last week. With [Learn from support](https://posthog.com/docs/business-knowledge/learn-from-support.md) on, that answer can be reused.
-   The handbook lives in GitHub. Select that repository and an agent can find the file by name, then read it.

Answers stay empty until two checks pass. See [Before answers can use a source](https://posthog.com/docs/business-knowledge/requirements.md).