Tasks
Org, project, use-case, provider, and user-scoped tasks with badge roll-ups.
NevarMail tracks setup and operational work as tasks. Every task belongs to your organization; a task may additionally be scoped to a project, a use case (always within its project), or a provider connection, and may be assigned to a user (assignment is orthogonal to scope).
Scope semantics
A task's scope is its most specific non-null scope:
| Scope | Meaning |
|---|---|
| Use case | Work tied to one use case (its project is always set too) |
| Project | Work tied to one project (includes its use cases' tasks in roll-ups) |
| Provider | Work tied to one provider connection |
| Organization | Everything else (e.g. onboarding tasks) |
The org-wide bell counts all open tasks. Scoped badges on the project switcher/context bar, use-case views, and provider cards count open tasks for that surface; clicking a badge opens the task list filtered to that scope.
API
GET /api/tasks and GET /api/tasks/summary accept optional projectId,
useCaseId, providerId (UUIDs) and assignedToMe=true (resolved to the
signed-in user — you can never query another user's assignments). The list
total always respects the filter. GET /api/tasks/scope-counts?dimension=project&ids=a,b,c
returns open-task counts per id (max 50 ids; every requested id is present,
zero-filled).