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

# Task Overview

> Learn how Tasks help you manage follow-ups, reminders, and actions directly within Custral.

# Overview

Tasks in Custral turn information into action.
They help your team stay organized by creating clear, trackable steps linked to your Records, Objects, or Workflows.
A follow-up on a lead, an onboarding call to book, a support issue to close: each is a Task on the record it came from, assigned to someone, with a due date.

***

## What Tasks do

Tasks represent specific actions or reminders assigned to users or Groups.
Each Task includes key details such as:

* **Title**: a short description of what needs to be done
* **Assignee**: the user or Group responsible
* **Due date**: when the task should be completed
* **Status**: open, in progress, or done
* **Priority**: Urgent, High, Medium, or Low (or None) to rank what matters most
* **Linked Entity**: the Record, Object, or View the task relates to

You can create Tasks manually or automatically through workflows, triggers, or automations.

***

## How Tasks fit in

Tasks are deeply integrated with the rest of Custral’s data model:

| Context                | Example                                       | Purpose                                      |
| ---------------------- | --------------------------------------------- | -------------------------------------------- |
| **Record-linked task** | Follow up with “Acme Corp” renewal            | Keeps actions tied to specific customer data |
| **Workflow task**      | Assign onboarding checklist after deal closes | Automates follow-up steps                    |
| **User task**          | “Review pipeline updates for Q1”              | Personal reminders or to-do items            |

Because Tasks are built as **Blocks**, they can be embedded, automated, or referenced across multiple surfaces: dashboards, workflows, and record pages.

***

## Task lifecycle

Each Task moves through a simple, flexible lifecycle:

1. **Created** – Task is added manually or triggered automatically.
2. **Assigned** – Responsibility is given to a user or Group.
3. **In progress** – Work begins and progress is tracked.
4. **Completed** – Task is marked done or resolved.
5. *(Optional)* **Archived** – Closed tasks are stored for reporting and history.

Task completion can also trigger follow-up automations, notifications, or next-step actions in your workflows.

***

## Prioritizing tasks

Every Task has a **priority**: **Urgent**, **High**, **Medium**, **Low**, or **None** (the default). Priority is a separate axis from manual ordering:

* **Priority** answers *how important* a Task is. Set it from the priority badge on the Task detail screen, or filter and sort by it in the Activity Center.
* **Manual order** (drag-and-drop) answers *where in your list* a Task sits.

The two work together. Task lists sort by **priority first** (Urgent → None), then by your manual drag order within each priority level, then by creation date. So an Urgent task always floats above a Low one, but you keep control of the order within a level.

Priority is color-coded everywhere it appears (the Activity Center, the Next Task widget, and the Home page), so the most important work is easy to spot at a glance.

***

## Conversation follow-ups

You can create a **follow-up** directly from a conversation. A follow-up is an ordinary Task linked to that conversation, so it inherits everything Tasks offer: priority, due date, assignee, and a place in your task lists.

1. Open a conversation and find the **Follow-ups** section.
2. Click **New follow-up**, give it a title, an optional due date, and a priority.
3. The follow-up appears in the conversation's Follow-ups list and in your normal task views.

Because follow-ups are Tasks, completing or reprioritizing one works exactly like any other Task.

***

## Collaboration and visibility

Tasks are visible wherever work happens:

* On linked **Record pages** for context
* Inside **Views and Dashboards** for status tracking
* Within **Workflows** for automation and reminders
* In **User task lists** for daily prioritization

Permissions follow the same ACL model as the rest of Custral, ensuring that only the right users or Groups can view or modify Tasks.

***

## Best practices

**1. Link Tasks to data**
Always associate a Task with a Record or Object so it stays contextual and easy to find.

**2. Automate repetitive steps**
Use workflows to create Tasks automatically when specific triggers occur (like a deal moving stages).

**3. Use clear titles**
Keep Task names short and action-oriented, like “Send contract to customer” or “Follow up after demo.”

**4. Review and close regularly**
Encourage your team to review open Tasks weekly to keep pipelines clean and up to date.

***

## Troubleshooting

**My tasks aren't sorted by priority.**
Lists sort by priority first, then by manual order. If you've applied a column sort (e.g. by Due Date) in the Activity Center, that overrides the default priority order. Clear the sort to return to priority-first ordering. Manual drag-and-drop is also disabled while a column sort is active.

**I set a priority but the badge shows "—".**
A dash means the Task's priority is **None** (the default). Open the Task and pick a level from the priority badge to set it.

**A conversation follow-up didn't appear.**
Follow-ups are linked to the conversation they were created from. Create them from that conversation's **Follow-ups** section. A Task made elsewhere won't show there unless it targets that conversation, and a newly created follow-up appears once the task list refreshes.

***

## Summary

Tasks turn your customer data into actionable steps.
By combining them with Custral’s Objects, Workflows, and permissions, you can keep every team aligned, accountable, and focused on what drives progress.


## Related topics

- [Tasks](/dev/webhooks/events/tasks.md)
- [Task Types](/team/tasks/types.md)
- [Overview](/data/objects/overview.md)
- [Navigation Overview](/surfaces/navigation/overview.md)