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

# Per-task Custom Fields in Project Templates

> Add custom fields to specific tasks within a project template so each task captures only the data it needs.

## Overview

Per-task custom fields let you scope a custom field to a specific task inside a project template — instead of having every task in the template show every field. Use this when different tasks in the same template need to capture different information.

For example, in a customer onboarding template you might have:

* A **Pick CRM Provider** task that captures the CRM name.
* A **Configure Account Filter** task that captures the filter string.
* A **Map ARR Field** task that captures the ARR field name.

Each task only shows its own field; it does not show the other tasks' fields.

## Prerequisites

* You can access **Settings → Object Manager**.
* You can access **Templates → Project Templates**.

## Set up a per-task custom field

**Step 1:** Go to **Settings → Object Manager → Projects/Tasks** and click **+ Create Field**.

**Step 2:** Pick a field type (Text, Pill, Number, Lookup, etc.), give it a name, and click **Save**. You do not need to associate the field with a task type or with a template here — per-task association happens in a later step.

**Step 3:** Go to **Templates → Project Templates** and open the template you want to edit (or create a new one).

**Step 4:** Click **Add Task** and fill in the standard fields (Title, Description, Duration). Leave the custom field inputs blank and click **Save**.

**Step 5:** Click the task you just created to open its detail view.

**Step 6:** In the **Custom Fields** section of the task, click **+** and pick the field you want this task to use.

The field is now scoped to that specific task. When someone fills in the task on a real project, this is the only field that appears for them. Other tasks in the template stay unaffected.

**Step 7:** Repeat steps 4–6 for each task that needs its own custom field.

## Tips

<Tip>
  A field can be added to more than one task if it makes sense — for example, a shared **Notes** field across several tasks. Each task keeps its own value.
</Tip>

<Note>
  You can mark the field as required, hidden, or read-only **per task** from the same Custom Fields section. The same field can be required on one task and optional on another.
</Note>

## What this is not

* **Not the same as the Customize panel.** "Customize → Task" on a template is a separate, template-wide setting; you do not need it for per-task fields.
* **Does not affect real (non-template) project tasks.** If you also want the field available on standalone project tasks, set that up under the field's task-type association in Object Manager.

## Troubleshooting

<Accordion title="The field doesn't appear when I click + on a task">
  Confirm the field was created under **Projects/Tasks** in Object Manager. Fields created under other entity types (Accounts, Opportunities, People) won't appear here.
</Accordion>

<Accordion title="The field is showing up on every task in my template">
  You probably added the field under **Customize → Task** on the template. That setting makes the field available template-wide. Remove it from Customize and add it per task instead.
</Accordion>

<Accordion title="The Add Task form is prompting me for a value at template creation">
  Leave the custom field blank when creating the task. Values are filled in per real project, not on the template itself.
</Accordion>