Workspaces and tasks
How daily operational work is organized, viewed, and completed in Whagons.
Workspaces are where teams operate. Tasks are the work moving through them.
What a workspace provides
Depending on tenant configuration and enabled features, a workspace can include:
- a sortable and filterable task grid;
- saved views and search;
- calendar, board, map, or timeline views;
- workspace chat and shared resources;
- KPI cards and operational summaries;
- creation controls limited to allowed task types and templates;
- task dialogs for details, forms, comments, attachments, approvals, and history.
The All Workspaces view brings together tasks a user can see across their normal and action-specific contexts.
Anatomy of a task
Common task data includes:
| Area | Examples |
|---|---|
| Identity | Human title, description, stable document ID, optional numeric task number. |
| Classification | Workspace, task type, template, team. |
| Location | Spot and optional coordinates. |
| Lifecycle | Status, priority, start date, due date, completion time. |
| People | Creator, reporter, assignees, mentioned users. |
| Structured work | Form responses and custom fields. |
| Collaboration | Comments, attachments, tags, messages. |
| Control | Approval, acknowledgment, SLA, transition rules. |
| History | Task log and status-transition timing. |
Typical task lifecycle
- A user, workflow, import, API integration, or agent creates the task.
- Whagons validates the workspace and task-type policy.
- Defaults from templates, statuses, priorities, and assignments are applied.
- Users work the task, add evidence, complete forms, and change allowed fields.
- Approval or acknowledgment steps appear when configured.
- A valid final status completes the task and records its history.
Visibility is contextual
Users do not automatically see every task in a tenant. Visibility can depend on:
- role permissions;
- team membership;
- workspace access;
- task ownership or assignment;
- reporter visibility;
- an approval or acknowledgment context;
- tenant-specific policy.
This same visibility model applies to Settings-issued API keys and delegated agent tokens because both act on behalf of a user.
One task, multiple action contexts
When another team needs to approve or acknowledge work, Whagons keeps the original task as the source of truth. The task can appear in an additional workspace with an action context, but its content, comments, attachments, approval state, and audit history stay connected to the same task.
This prevents conflicting copies and gives integrations one stable task to reference.
Finding a task
In the product, users can search and filter workspace grids. In the API, clients can fetch by the task's document taskId, by its numeric pgId when present, or list tasks using workspace, status, priority, team, spot, template, assignment, and text filters.
See Task API operations for technical details.