Tasks

Norbital includes a built-in task system for coordinating work around records, approvals, and internal operational queues. It is useful when a workflow needs ownership and follow-through, not just a data state change.

What Tasks Are Good For

  • reviewing high-value or high-risk records,
  • coordinating work across teams,
  • managing deadlines and operational queues,
  • tracking parent-child work items,
  • keeping action items linked to the underlying data model.

Core Concepts

Hierarchical tasks

Tasks can be nested so you can model broader workstreams and the individual actions beneath them.

Assignment model

Tasks support:

  • direct user assignees,
  • team assignment.

Linked records

Tasks can link to tenant records such as projects, invoices, suppliers, or approvals so work stays anchored to the underlying operational object.

Views

Norbital supports kanban, list, timeline, and task detail views so teams can work in the style that best fits the workflow.

Access Model

Task visibility is assignment-based rather than driven by collection route permissions. In practice, that means a user usually sees a task because it is assigned to them or one of their teams.

  • Admins can see all tasks unless impersonating.
  • Non-admins see tasks assigned to them directly.
  • Non-admins also see tasks assigned to their teams.

Descendant visibility is inherited downward, so when a parent task is accessible its child work can remain visible in hierarchy views as well.

Task visibility and record visibility are separate
A user may be allowed to see a task but still have restricted access to the linked record. In that case, the task remains visible while the linked record can appear as restricted, missing, or deleted.

TaskBlock Integration

You can embed tasks directly into page UI blocks using SDK.TaskBlock, which is useful for operational dashboards and department work queues.

A simple use case is an app page that shows the current team queue beside key collection data.

  1. Use tasks for work that needs an owner, due date, or follow-up sequence.
  2. Link tasks to the underlying operational record when context matters.
  3. Assign at the parent level when an entire workstream should be visible to a team.
  4. Embed task views in app pages when the team needs a persistent queue surface.
Previous Automations Next Commander