Project Templates Guide

Project templates are blueprints for creating new Kodexa projects with predefined resources, configuration, and workspace setup. They should prepare the project boundary for a business process; Activity Plans should define the automated work that runs inside that boundary.

What You’ll Learn

This guide covers:

When to use a project template
Which resources belong in a template
How templates support Activity Plans, Tasks, Data Definitions, Data Forms, and project workspaces
How to test a template before using it in production

Activity-First Template Model

Use this split when designing templates:

Concern	Where it belongs
Automated work, dependencies, branches, scripts, bridge calls, LLM steps, approvals	Activity Plan
Human review setup, queue metadata, review status model	Task Templates and Task statuses
Extracted business data model	Data Definitions
Review and correction UI	Data Forms
Project-specific document storage and workspace panels	Project Template
Shared business knowledge and classification context	Knowledge Sets

Quick Example

slug: invoice-operations
orgSlug: acme
version: 1.0.0
name: Invoice Operations
type: projectTemplate
description: Workspace setup for AP invoice intake and review

stores:
  - slug: "${project.id}-intake"
    name: "Invoice Intake"
    description: "Upload incoming invoices here"
    storeType: DOCUMENT
    storePurpose: OPERATIONAL

taskStatuses:
  - slug: ready-for-review
    label: Ready for Review
    statusType: TODO

  - slug: complete
    label: Complete
    statusType: DONE
    locked: true

taskTemplates:
  - slug: invoice-review
    name: Invoice Review
    description: Review extracted invoice fields and resolve exceptions

dataForms:
  - ref: "acme/invoice-review-form"

taxonomies:
  - ref: "acme/invoice"

workspaces:
  - name: Review Workspace
    slug: review
    workspaceStorage:
      availablePanels:
        documentStores: true
        dataForms: true
        taxonomies: true
        exceptions: true
        auditEvents: true

Deploy with:

kdx deploy invoice-operations.yaml

Template Use Cases

Project templates are useful when you need to:

Onboard a new business unit to an existing Activity Plan
Recreate the same workspace structure for multiple customers or teams
Standardize document stores, statuses, Data Forms, and Task Templates
Bind a project to shared Data Definitions and Knowledge Sets
Keep workspace configuration reviewable as source-controlled metadata

Documentation Structure

Build Project Templates

Build an activity-first template step by step.

Template Structure Reference

Look up supported sections and fields.

Next Steps

Read Activity Plans to understand the automated work model.
Use Project Template Structure as the field reference.
Build your first template with Build Kodexa Project Templates.

Formulas Guide Build Kodexa Project Templates

⌘I

Introduction

Activity Plans

Triggers

Task Templates

Task Groups

MCP Connector

Data Definitions

Excel Processing

Scripting

Intakes

Formulas

Project Templates

Data Forms

Working with Claude Code

Working with Kodexa Agent

Reference

What You’ll Learn

Activity-First Template Model

Quick Example

Template Use Cases

Documentation Structure

Build Project Templates

Template Structure Reference

Next Steps

​What You’ll Learn

​Activity-First Template Model

​Quick Example

​Template Use Cases

​Documentation Structure

Build Project Templates

Template Structure Reference

​Next Steps

What You’ll Learn

Activity-First Template Model

Quick Example

Template Use Cases

Documentation Structure

Next Steps