Browse documentation

Tasks

The mental model for tasks: tracked work connected to your data.

A task is a unit of tracked work. On its own that sounds like any to-do list, but in Spark a task's value is that it lives next to the data it's about, so operational work stays connected to its context instead of drifting off into a separate tool.

What a task carries

A task holds the properties you'd expect for tracking work: an assignee (who owns it), a status (where it stands), a priority, a due date, and labels. Statuses aren't fixed by Spark; they're defined for your workspace, so a team can model its own process rather than bend to someone else's.

Connected to its context

The part that matters is the connection. A task can be linked to a canvas, so the dashboard that gives the task meaning travels with it. Someone picking up "Review Q3 counterparty exposure" opens the task and has the relevant picture right there, rather than hunting for which view to look at.

This is what keeps work and data together: the task tracks the doing, and the linked canvas supplies the seeing.

Where tasks show up

Tasks have their own place in the workspace, and they can also appear on a canvas as a widget, so a dashboard for a use case can show the open work alongside the numbers. A workflow can create tasks too, which is how automated processes hand work back to people at the right moment.

The Tasks section covers how to create, assign, and link tasks.