---
title: "Managing tasks"
manual: "LLM Foundation"
version: "0.42"
permalink: "https://docs.typo3.org/permalink/netresearch/nr-llm:administration-tasks@0.42"
source: "Administration/Tasks.rst"
rendered: "2026-11-01T11:38:21+00:00"
---

# Managing tasks {#administration-tasks}

Tasks are one-shot prompt templates that combine a
configuration with a specific user prompt. They
provide reusable AI operations that editors or
extensions can execute with a single call.

![Task list showing task name, linked configuration, description, and actions](../Images/backend-tasks.png)

## Adding a task manually {#administration-tasks-add}

1.  Navigate to **AI > Authoring >
    Tasks**.
1.  Click **Add Task**.
1.  Fill in the required fields:

    -   ****Name****

        Display name (e.g., `Summarize Article`).

    -   ****Configuration****

        Select the LLM configuration to use.

    -   ****User Prompt****

        The prompt template. Use `{{input}}` for the task's input.
        PHP callers of `Task::buildPrompt()` can supply other named
        variables; placeholders without a supplied value remain unchanged.
1.  Add a description so other admins understand
    what the task does.
1.  Click **Save**.

## Executing a task {#administration-tasks-execute}

Inactive tasks stay visible in the administrator catalogue. If none of its
non-deleted tasks are active, the catalogue displays an activation warning.

Click **Run** on any task to open the
execution form. It shows the configuration, model,
parameters, input field, and prompt template.

![Task execution form showing configuration details, input field, and prompt template](../Images/backend-task-execute.png)

Example tasks:

-   **Summarize content** — condense long articles.
-   **Generate meta descriptions** — SEO optimization.
-   **Translate text** — one-click translation.
-   **Extract keywords** — pull key terms from content.

## The editor module {#administration-tasks-editor-module}

Editors do not need backend administrator rights to run tasks: the
dedicated **AI > AI Tasks** module ([ADR-131](https://docs.typo3.org/permalink/netresearch/nr-llm:adr-131@0.42))
lists every active task and opens a slim run form — without any of the
management affordances of this admin module. Access takes both switches
described under [Backend user permissions](https://docs.typo3.org/permalink/netresearch/nr-llm:administration-permissions@0.42): the module permission
on the backend group AND the *Execute AI tasks* grant. Every run is
pre-flighted against the user's own [usage budget](https://docs.typo3.org/permalink/netresearch/nr-llm:administration-user-budgets@0.42). Tasks with the `table` input type are
not offered to editors — their database record picker stays admin-only.

![The editor-facing AI Tasks module listing runnable tasks grouped by category](../Images/backend-aitasks-list.png)

![The editor run form with input area and output panel, without management links](../Images/backend-aitasks-execute.png)

### Usage, budget and cost estimate {#administration-tasks-editor-usage}

Both views of the module show the editor's own AI usage in a
**Your AI usage** panel: requests, tokens and cost, today and
this month. The windows and numbers are the ones the budget check
compares — today from 00:00, this month from the first day of the month,
both in server time — read from the same usage table. An editor sees
only their own numbers.

When the editor has an active [budget record](https://docs.typo3.org/permalink/netresearch/nr-llm:administration-user-budgets@0.42) with at least one limit, each limited
value shows "used of limit" and a progress bar; an axis with a limit of
`0` reads "no limit". Without such a record (none, switched off, or
every limit `0`) the panel says that no personal limit is set and still
shows the usage. Costs are in USD, as in the
[Analytics module](https://docs.typo3.org/permalink/netresearch/nr-llm:administration-analytics@0.42); the used cost is an
estimate and carries a `~`.

The run form adds **Cost of one run**:

-   A price range for one run with the configuration the run uses. The
    lower value assumes no answer, the upper value an answer of the full
    length the configuration allows (its maximum tokens). A range needs an
    input price and an output price on the model and a maximum answer
    length on the configuration; otherwise the form says that the cost
    cannot be estimated.
-   For an automatic task the estimate includes the data shown when the
    page was loaded. For a manual task it covers the task's instructions
    without the editor's input, and the form says so. Skills and
    instructions the run adds are not counted, so the real input is
    higher.
-   Whether the next run passes the budget. The form names the limit,
    without numbers, in two cases: the run will be refused because a limit
    is already reached, or the run can start but would exceed a limit at
    the upper cost estimate. A configuration's daily limit counts the
    usage of all users of that configuration.

After a run the panel and the verdict are read again, so the numbers
include that run.

> [!TIP]
> Use the [Task wizard](https://docs.typo3.org/permalink/netresearch/nr-llm:administration-wizards-task@0.42) to generate
> a complete task (including a new configuration)
> from a plain-language description.