Skip to main content

Platform

Task boards

Plan event work and standalone operations with assignments, collaboration, and lifecycle controls.

What a task board organizes

A board groups tasks for an event or a standalone community operation. Event-linked boards inherit the event title and cannot be archived independently; standalone boards have their own name, description, visibility, and archive action.

Board lifecycle

StateBehavior
ActiveNormal planning, collaboration, and eligible automation.
PausedBoard remains visible; automation is suppressed until resumed.
CompletedBoard remains as history; automation is suppressed and the board can be reopened.
ArchivedStandalone board and active tasks leave the active workspace; automation cannot execute.

Tasks and status

Tasks move among To do, In progress, and Done. They can carry a description, Low/Medium/High priority, label, due date, order, and one or more assignees. Completed tasks remain in board history and can be moved again by an authorized operator.

For administrators

  • Create standalone or event-linked boards and control Public or Private visibility.
  • Create, edit, assign, reorder, move, and archive tasks; use reusable task templates where appropriate.
  • Pause, complete, resume, or reopen a board using the allowed lifecycle transitions.

For members

Members can view boards available to them and see whether they are assigned or viewing. An assigned member can move their task, add comments and attachments, and create, edit, complete, reopen, reorder, or archive checklist items. Unassigned viewers cannot perform those assigned-member changes.

Comments, attachments, checklists, and activity

Each task keeps a chronological activity history for assignment, status, priority, due date, content, comments, attachments, checklist work, archival, and reordering. Task attachments are normal protected task files; they are not encrypted-chat attachments and should be handled according to community data policy.

Visibility and access

Public boards are visible in the member board list. Private boards are visible to assigned members. Administrative reads and changes remain permission-checked, and all member task actions verify the current community and assignment where required.