> For the complete documentation index, see [llms.txt](https://docs.teleskope.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teleskope.ai/the-platform/policy-document-ingestion.md).

# Policy Document Ingestion

> Policy Document Hub may not be enabled for your organization yet. Contact your Technical Account Manager to enable.

## What is Policy Document Ingestion?

**Policy Document Ingestion** lets you upload your organization's actual written policies, such as retention schedules, classification standards, DLP policies, regulatory text, directly into Teleskope. Teleskope reads each document, extracts the individual statements inside it, and recommends the document types and policies that operationalize them.

Every recommendation is traceable back to its source: the specific document, page, and quoted text that produced it.

Nothing is applied automatically — recommendations sit in a review queue until you accept a document type or create a policy from it.

***

## What Would You Use It For?

Turning a written policy into an enforced rule has traditionally been a manual translation step: someone reads the document, decides what it means for your data, and hand-configures the corresponding document types and policies. Policy Document Ingestion removes that translation step.

Common use cases include:

* **Bootstrapping document types from an existing policy** — upload a classification standard and get back a set of recommended document types grounded in what it actually says, instead of starting from scratch in Document Type Manager
* **Turning a retention or DLP policy into policy recommendations** — get suggested Policy Maker workflows (triggers, filters, and actions) based on what your policy document describes, refined to only what's actually buildable on your enrolled connectors
* **Reviewing evidence before committing** — every suggested document type or policy links back to the exact clause it came from, so you can verify before accepting

***

## Navigating to Policy Document Ingestion

**Policy Document Hub** is its own item in the left-hand navigation, right after Policies.

1. Click **Policy Document Hub** in the left-hand navigation
2. You'll land on the **Collections** view, showing any policy document collections you've created

***

## Creating a Collection and Uploading Documents

Policy documents are organized into **collections**. There are no default collections — you create them explicitly.

1. Click **Create collection** and give it a name (for example, "2026 Data Retention Policy")
2. Open the collection and click **Upload document**
3. Select a file — Teleskope currently accepts **PDF, XLSX, and CSV** formats
4. Teleskope begins extraction automatically. You can preview the original document (including a PDF preview) while extraction runs

If you have more than one policy document, upload them separately into the same collection — recommendations are generated from all extracted documents in the collection together.

If extraction fails in a retryable way, a **Retry** option is available on the document.

***

## Reviewing Recommendations

Once extraction finishes, Teleskope surfaces two kinds of recommendations based on the statements it found in your document: **document type recommendations** and **policy recommendations**.

You can generate either kind in any order, but for the best results, generate document type recommendations first, accept the ones you want, and then generate policy recommendations. Policy recommendations are built to take advantage of your existing document types, so running them after your document types are in place means they can reference the tags you just accepted, rather than potentially recommending a policy around a document type that doesn't exist yet.

### Document Type Recommendations

These are candidate document types — the same kind of object you'd otherwise create manually in [Document Type Manager](/the-platform/document-type-manager.md) — generated from the content of your policy document.

Each recommendation shows:

* A proposed display name and description
* **Evidence** — the specific document, page, and quoted text the recommendation was extracted from

From the review queue you can:

* **Accept** a recommendation, choosing a sensitivity at the time of acceptance, to add it to Document Type Manager
* **Hide** a recommendation you don't want (and **unhide** it later if you change your mind)
* **Unaccept** a previously accepted recommendation, removing it from Document Type Manager
* **Retry sync** if syncing an accepted type to Document Type Manager failed

If generation itself fails, or you want a fresh set of suggestions, use **Regenerate** at the collection level rather than retrying an individual recommendation.

### Policy Recommendations

Teleskope also evaluates whether a policy document's statements can become an actual Policy Maker workflow. Each policy statement is broken down into:

* **Trigger conditions** — the subject(s) involved, and any sharing, accessibility, or staleness attributes described
* **Filter conditions** — any location or scope attributes
* **Data store** — the data store(s) or file type(s) the statement refers to, if specified
* **Workflow** — any alerts, deferrals, or actions the statement implies

Before a recommendation is shown, Teleskope checks whether it's actually buildable: whether the trigger conditions are representable, whether the target data store is an enrolled connector, and whether the required action can be applied or reasonably approximated (for example, Teleskope can't shred a physical copy, but it can quarantine a file).

Click **Create policy** on a recommendation to turn it into a policy. You can set its **Severity** first. Created policies live in Policy Maker and are editable and versioned like any other policy.

***

## What Happens If You Delete a Source Document

Accepted document types are durable. If you delete the source document, the type stays in Document Type Manager with its evidence intact — you just won't be able to preview the original page anymore. "View source" will note that the source document was deleted or modified, but the quote itself is preserved.

The **Unlinked** tag means something different: it appears when a Hub-generated type is later edited in Document Type Manager (its name or description changed) or its category is deleted. That edit permanently detaches the type from its source policy document — it can't be restored.

***

## Using Policy Document Ingestion Across the Platform

Recommendations you accept flow directly into the same systems every other document type and policy in Teleskope lives in:

* **Document Type Manager** — accepted document type recommendations appear in the Overview tab alongside manually created and AI-generated types, with the same tagging and dry-run capabilities. One caveat: renaming a Hub-generated type or editing its description detaches it from its source policy document permanently — the type itself is unaffected, but it can no longer be traced back to the clause that produced it.
* **Policy Maker** — policies created from recommendations are editable and versioned like any other policy
* **Data Catalog & Data Explorer** — once applied, document types recommended from your policy documents can be used to filter and search your data like any other document type