Staff tasks and assignment

Tasks are internal staff to-dos. They're never visible to members — only staff see them. A task gets created one of two ways: someone creates it by hand, or a workflow's Create a task step creates it automatically when its trigger fires. Use New task when you need to add one yourself.

Open Tasks from the dashboard's My tasks card, or search for it (Cmd-K). Three labeled filter groups:

• View — List (default) or Board. Board view shows the same tasks as columns by state (Open, In progress, Done, Dismissed); click Complete or Dismiss on an open card to move one. Both views use the same action labels; dismissing asks for confirmation.

• Show — Mine: everything assigned to you or your role that's still open (the default). All: every task in the org, paginated.

• Status — Open, Done, or Dismissed (list view only; board shows all four states as columns).

To add one by hand, click New task: give it a title, an optional body (Markdown supported), a priority (Normal/High), an optional assignee, and an optional due date.

A task can be owned by a role (e.g. Manager) or by one specific person. Never both, and it can also be unassigned. The assignee dropdown (on New task and on each row's reassign control) lists roles first, then staff members by name; pick whichever fits. Assigning to a role keeps ownership with whoever is covering that role this season; assigning to a person is for something only they should pick up. Reassigning always replaces the current assignee, whichever kind it was.

A task can be configured (usually by a workflow's Create a task step, via its "closes on" event field) to close itself automatically once a chosen event happens later. E.g. a task nudging staff to follow up on an unpaid invoice can auto-close when that same invoice is later paid or voided. This runs for every domain event the platform tracks, whether the task was created by a workflow or by hand from the tasks list, usually within a few minutes of the event.

Known limitation: the auto-close only fires when the task's own subject — the invoice, membership, household, or user it's anchored to — matches the closing event's subject exactly. A workflow-created task is anchored to the most specific one of those four resolved when it was created (invoice takes priority, then membership, then household, then user); if the closing event you picked belongs to some other kind of subject (a payment or a ticket, for example), it can never match and the task will sit open until someone closes it by hand. If a task you expected to auto-close is still open, check that its "closes on" event actually shares a subject type with something the task is anchored to.

A single workflow can create at most 100 tasks per day. Beyond that, the workflow holds the rest until the next day rather than flooding the queue. If a task you expected from a workflow is missing, check whether that workflow hit its daily limit (see Workflows and the dry-run gate for what happens when it does).