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.Documentation Index
Fetch the complete documentation index at: https://developer.kodexa.ai/llms.txt
Use this file to discover all available pages before exploring further.
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
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.
