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

# Templates

> Reusable, versioned configurations that standardize prompt, schema, data quality, notifications, and frequency across workflows

Templates let you define a reusable configuration (prompt, schema, data quality rules, notifications, and run frequency) and apply it to multiple workflows. When you update the template, you can push changes to all linked workflows at once.

A template can include any combination of these parts:

| Part              | What it controls                              |
| ----------------- | --------------------------------------------- |
| **Prompt**        | The extraction instructions for the AI agent  |
| **Schema**        | The field definitions and entity name         |
| **Data quality**  | The per-field validation rules                |
| **Notifications** | Event subscriptions and notification channels |
| **Frequency**     | How often linked workflows run                |

Each part is optional. For example, a template can define only a schema, or a schema and notifications without a prompt.

## Versioning

Templates are versioned. Every time you save changes, a new version is published. Versions are immutable. Once published, a version cannot be edited.

This means you can:

* Roll out updates to linked workflows selectively
* Roll back to a previous version if needed
* See exactly what changed between versions

## Linking Workflows

When you link a workflow to a template, the template's configuration is applied to the workflow. The configuration managed by the template becomes **read-only** on the workflow, and you can manage it through the template UI instead.

To modify a template-managed field on a workflow, either update the template and apply the change, or unlink the workflow first.

<Note>
  Unlinking a workflow preserves its current configuration. The workflow keeps the prompt, schema, and notifications it had. They become editable again from the workflow itself.
</Note>

## Managing Templates

<CardGroup cols={2}>
  <Card title="In the UI" icon="window" href="/docs/ui/templates">
    Create and manage templates visually in the dashboard.
  </Card>

  <Card title="Via API" icon="code" href="/docs/sdk/templates/overview">
    Create and manage templates programmatically with the REST API or MCP Server.
  </Card>
</CardGroup>

## Learn More

* [Schemas](/docs/workflows/schemas): Field definitions and data types used in template schemas
* [Notifications](/docs/notifications): Event types and channels used in template notifications
* [API Reference](/api-reference/templates/list-templates)