Skip to main content
Teio is built to adapt to your team’s processes rather than forcing you to adapt to a fixed structure. You can add custom fields to capture data specific to your workflow, define the status columns that reflect your real stages, automate repetitive handoffs with rule-based automations, save filtered views for fast access, and package recurring project structures into templates for one-click reuse.
Custom fields, workflow automations, and templates are available on the Pro plan and above. Saved views and custom task statuses are available on all plans, including Free.

Custom fields

Custom fields let you attach structured data to tasks and projects beyond the built-in properties. You can add them at the project level, and they appear on every task within that project.

Field types

A free-form single-line or multi-line text input. Use text fields for short notes, external reference numbers, stakeholder names, or any unstructured string data that does not fit a predefined list.
  • Single-line: Best for short values like a ticket ID or a client name.
  • Multi-line: Supports longer content such as acceptance criteria or context notes.
Stores a numeric value. Number fields support integers and decimals. Use them for story points, budget figures, hours estimates, or priority scores. You can optionally set a unit label (for example, pts or hrs) that displays alongside the value.
A date picker field for capturing a specific calendar date. Date fields are independent of the built-in due date — use them for tracking external deadlines, review dates, launch dates, or any other milestone that matters to your workflow. Dates can also be used as trigger conditions in automations.
A dropdown that allows exactly one value from a predefined list of options. Use select fields when a task can only be in one state at a time — for example, a Priority field with options Low, Medium, High, and Critical. You can define and reorder options at any time; existing values are preserved when you rename or reorder options.
A dropdown that allows multiple values to be chosen simultaneously. Use multi-select fields for tagging tasks with categories, affected platforms, team areas, or any attribute where more than one value can apply. Values appear as removable chips on the task card and can be used as filter conditions in views.
A boolean true/false toggle. Use checkbox fields for simple binary attributes: whether a design review is complete, whether a legal sign-off has been obtained, or whether a feature is flagged for a demo. Checkbox fields render as a checkmark on task cards when enabled.

Creating a custom field

1

Open project settings

Navigate to the project where you want to add the field. Click the menu in the project header and select Project settings, then go to the Fields tab.
2

Add a new field

Click Add field. Enter a field name and select a field type from the dropdown. For Select and Multi-select fields, add your list of options — one per line. Click Create field when done.
3

Set a default value (optional)

After creating the field, click the field row and toggle on Set default value. New tasks created in this project will automatically populate the field with the value you specify.
4

Reorder fields

Drag fields in the list to control the order they appear on task detail panels. Changes apply immediately for all members of the project.

Custom task statuses

Task statuses represent the stages a task moves through in your workflow. Teio comes with a default set (To do, In progress, Done), but you can fully replace or extend these per project. To manage statuses, go to Project settings → Statuses. From there you can:
  • Add a status — click Add status, enter a name, and choose a color. New statuses are added to the end of the column order by default.
  • Rename a status — click the status name to edit it inline.
  • Reorder statuses — drag statuses into the column order that matches your workflow stages.
  • Mark a status as completed — toggle Mark as complete on any status to treat tasks with that status as done for the purposes of progress calculations and filters. You can have more than one completing status (for example, both “Done” and “Cancelled”).
  • Delete a status — click Delete on a status and choose a replacement status for any existing tasks currently using it.

Workflow automations

Automations let you define rules that execute actions automatically when certain conditions are met, eliminating repetitive manual updates and handoffs. Each automation rule follows a trigger → condition → action structure:
PartDescriptionExample
TriggerThe event that starts evaluationTask status changes
ConditionAn optional filter narrowing when the rule firesNew status is “Done”
ActionWhat Teio does automaticallyNotify assignee, set a field, create a subtask

Creating an automation rule

1

Open the Automations panel

Navigate to your project and click Automations in the project toolbar, or go to Project settings → Automations. Click New rule.
2

Choose a trigger

Select what event will activate the rule. Available triggers include:
  • Task status changes
  • Task is created
  • Due date arrives or passes
  • A custom field value changes
  • A specific member is assigned
3

Add conditions (optional)

Narrow when the rule fires by adding one or more conditions. For example, if your trigger is Task status changes, you can add the condition New status is “Done” so the rule only fires on that specific transition, not every status change.
4

Define actions

Choose one or more actions to execute. Available actions include:
  • Notify assignee or a specific member — sends an in-app and/or email notification
  • Change task status — moves the task to another status automatically
  • Set a field value — updates a custom or built-in field (for example, set Priority to High)
  • Assign to a member — assigns or reassigns the task
  • Create a subtask — generates a new subtask with a specified name and optional assignee
  • Post a comment — adds an automated comment to the task activity feed
5

Name and activate the rule

Give your rule a descriptive name so your team understands its purpose at a glance (for example, “Notify assignee when marked Done”). Toggle the rule to Active and click Save. The rule takes effect immediately for new trigger events.
Start with a single action per rule while you test behavior. Once you confirm the rule fires as expected, you can add additional actions or chain rules together to build more complex workflows.

Saved views

Views let you apply a combination of filters, grouping, and sorting to your task list and save the result so you can return to it instantly. Every team member can create personal views, and Admins can pin shared views for the whole project. To create a saved view:
1

Configure your task list

In any project’s task list, use the Filter, Group by, and Sort controls in the toolbar to set up the view you want. For example: filter by Assignee = me, group by Status, sort by Due date ascending.
2

Save the view

Click Save view in the toolbar. Enter a name for the view and choose whether it is Personal (visible only to you) or Shared (visible to all project members). Click Save.
3

Access saved views

Saved views appear in the project sidebar under Views. Click any view to instantly apply its configuration. Personal views are marked with a person icon; shared views are visible to all members.

Templates

Templates let you save a project or task structure and reuse it for future projects or recurring work, preserving custom fields, statuses, task lists, and automation rules without duplicating data.

Project templates

Save an entire project — including its statuses, custom fields, sections, and task structure — as a template. When you create a new project, choose From template to pre-populate it with this structure instantly.

Task templates

Save a single task and its subtasks as a template. Use task templates for recurring deliverables like onboarding checklists, bug report structures, or content production tasks.
Creating a project template Open the project you want to save, click in the project header, and select Save as template. Give the template a name and optionally add a description to help teammates understand when to use it. The template is saved to Settings → Templates → Projects and is available to all workspace members. Creating a task template Open any task, click in the task detail panel, and select Save as template. The template captures the task name, description, subtasks, custom field defaults, and checklist items. Task templates are available when creating a new task by clicking Use template in the new task dialog. Editing and deleting templates Manage all templates under Settings → Templates. Click any template to preview its structure, rename it, or delete it. Deleting a template does not affect projects or tasks that were previously created from it.
Template contents are visible to all workspace members. Avoid saving sensitive client names, internal cost figures, or confidential process details directly in template task names or descriptions.