> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/administration/task-types.md).

# Task Types

Task Types are reusable definitions for common work. They determine how a task is created, what information it asks for, and what completion output may be required.

Task Type management is an Administration responsibility. Members use task types through the visible task creation options in Inbox and Projects.

Use Task Types when a workflow should be repeatable instead of recreated from scratch each time.

## What A Task Type Contains

A Task Type can include:

* Name and slug
* Category
* Description
* Input fields
* Schema
* Required resources
* Execution defaults
* Output expectations
* Completion requirements
* Schedule configuration

## Definition And Schema

The Task Types surface separates reusable task metadata from the shape of task inputs and outputs.

**Definition** covers the human-readable task type: what it is for, when to use it, and how it should behave.

**Schema** describes structured fields and output contracts. Schema matters when a task needs validated inputs or required completion output.

In the Task Types manager, the **Definition** view can include fields such as name, slug, category, description, subtask settings, agent turn budget, execution context, required resources, execution profile, and definition JSON. The **Schema** view is where structured input and output contracts belong.

Some task types also expose **Schedules**. A schedule can make tasks from that definition run on a managed cadence, and the schedule health summary can show active, due, pending, completed, or failed execution state.

## When To Create A Task Type

Create or refine a Task Type when:

* The same workflow happens repeatedly
* The task needs specific input fields
* Completion needs a structured output
* Project setup should create consistent tasks
* Automation or agent workflows need a predictable task contract

## Managing Task Types

Task Type management is usually handled by workspace administrators, setup authors, or pack maintainers. Only change a task type when you understand how it is used. A task type can affect future tasks and, depending on the implementation, may also affect how existing tasks are interpreted.

When updating a task type:

1. Confirm the task is still needed.
2. Review the definition and schema together.
3. Preserve fields that existing workflows depend on.
4. Test creation and completion before relying on the change.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/administration/task-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.