DDeetzo Academy ◀ All module guides
Deetzo ERP · Tasks & Collaboration · Training Guide

Tasks & Collaboration — where the team works

The task is Deetzo's atom of work — owned, dated, and pinnable to any record. Collaboration wraps it: comment threads with @mentions on every record, an Inbox that gathers what's aimed at you, and email + push when someone needs you.

Version 1.2 Reviewed against production code All plans Audience Everyone
01Anatomy
→
02Lifecycle
→
03On records
→
04Reminders
→
06Collaborate
→
07Inbox
00

The big picture

Two things in one guide: the task — a unit of work that can live anywhere — and collaboration — the comment threads and mentions that wrap around any record.

A task is Deetzo's atom of work. It has an owner, a due date, a status, and it can hang off anything — a standalone to-do, a step inside a project, or a follow-up pinned to an invoice, a quote, a customer or a supplier. Collaboration is the layer on top: threaded comments with @mentions on records across the whole app, an Inbox that collects what's aimed at you, and email + push when someone needs you.

erp.deetzo.com/#/tasks
Tasks workspace with KPI tiles (Open, Overdue, Unassigned), view-mode toggle (My Day, List, Board, Deadline, Dashboard), status filter chips, a label filter, and a task table with links out to leads and projects
ScreenTasks workspace. KPI tiles (Open / Overdue / Unassigned), a view switcher — My Day · List · Board · Deadline · Dashboard — status chips and a label filter, over a table where each task links back to the lead or project it belongs to.

Where the screens live

  • Tasks workspace — /tasks. The cross-cutting view of every task you can see. Task create/edit and the task detail open as pushed screens, not their own URLs.
  • Inbox — /inbox. Everything addressed to you — mentions and thread activity — grouped by the record it happened on.
  • On any record — a Tasks section is embedded on leads, quotes, invoices, customers, suppliers, purchase orders and vendor bills; a discussion thread on leads, tasks, quotes, sales orders, invoices, purchase orders and work orders. There's no separate URL; they live inside the record you're already looking at.
One mental model

Tasks and Inbox are not gated by a route guard — anyone signed in can open them. What you actually see inside is filtered by permissions and by whether the task or thread is yours (§08). The screen is open; the data is scoped.

01

Anatomy of a task

Everything one task can carry.

erp.deetzo.com/#/tasks · TK-0003
Task detail for TK-0003 showing description, checklist, sub-tasks, attachments and an activity timeline on the left, with a right rail for Status, Priority, Due date, Assignee with Reassign, Participants, a Dependency predecessor, and a linked Project with milestone
ScreenTask detail (TK-0003). Left: description, checklist, sub-tasks, attachments, and a full activity timeline. Right rail: status · priority · due date, assignee (with Reassign), participants, a dependency predecessor, and the project + milestone it belongs to. "Mark complete" is one click in the header.
FieldWhat it does
NumberTK-0001 — assigned atomically from a per-tenant counter, so numbers never collide or repeat.
AssigneeThe one person who owns it. Reassign is a single action and is logged to the activity trail.
Prioritylow · medium · high — a plain flag, drives sort and the KPI tiles.
Due date + reminderA deadline plus a reminder offset (see §04). Overdue tasks feed the Overdue KPI.
ChecklistLightweight tick-items inside the task — good for a definition-of-done that isn't worth a sub-task.
Sub-tasksChild tasks (parentTaskId) — a task can break into smaller tasks that roll up to it.
ParticipantsPeople beyond the assignee who watch the task and can be reminded and notified.
DependencyA single finish-to-start predecessor. It's advisory — Deetzo surfaces it, it does not hard-block you from starting.
Record linkThe record the task hangs off — an invoice, quote, customer, supplier, purchase, vendor bill, or a project + milestone (§03).
ExtrasAttachments (files or a ZIP), custom fields, labels/tags, and a recurrence rule (§04).
02

The task lifecycle

Seven states — richer than "todo / done".

Pending→ In Progress→ In Review→ Completed
On Hold· Cancelled· Re-Opened

The status set is pending · inProgress · onHold · inReview · completed · cancelled · reOpen. The happy path runs Pending → In Progress → In Review → Completed, but you can park a task On Hold, Cancel it, or reopen a finished one (Re-Opened, which has its own column on the Board). Every status change is stamped into the task's activity timeline with who and when — TK-0003 above shows exactly that history.

Pending not started In Progress start time noted In Review done, needs check Completed finish time noted Cancelled reminders stop On Hold parked Re-Opened back on the board start submit sign off pause resume Reopen back to work Cancel The status menu can jump to any status; the arrows are the usual path. Completing a task after its deadline pushes dependent tasks out by the same delay. Completing a repeating task neither creates nor ends the next copy (see §04).
LifecyclePending → In Progress → In Review → Completed is the usual path; nothing forces it. Pick any status from the status pill on a task, or drag it between columns on the Board. Mark complete jumps straight to Completed and Reopen task puts it back to In Progress. On a project task, the project's Status workflow can grey out some moves in that menu.
In Review is the useful one

The extra In Review state lets an assignee say "done, needs a check" without prematurely closing the task — the reviewer moves it to Completed (or Re-Open) after looking.

03

Tasks on any record

A follow-up that lives where the work is.

The same task object attaches to business records, so a to-do sits on the thing it's about instead of floating in a separate list. Open an invoice, a quote, a customer, a supplier, a purchase order or a vendor bill and you'll find a Tasks section with an Add follow-up action; leads have their own Tasks tab. (Work orders carry a discussion thread, but no Tasks section.)

Chase a payment

On an overdue invoice, add "Call about payment" due Friday — it shows on the invoice and in your Tasks workspace and My Day.

Work a deal

On a lead or quote, "Send revised pricing" keeps next-steps attached to the opportunity, not lost in a notebook.

Fix a supplier issue

On a PO or supplier, "Follow up on short shipment" so the reminder travels with the record.

These are the same tasks: they roll into the KPI tiles, the Deadline view, reminders and the Board. The record link is just where they surface. A task created on a record can still be reassigned, given a checklist, or promoted with sub-tasks like any other.

04

Reminders & recurrence

Automatic nudges, and tasks that come back.

The reminder offset

Every task with a due date carries a reminder offset — how long before the deadline Deetzo should nudge. An hourly check looks for tasks entering their reminder window and sends a push notification and a bell alert to the assignee (and, with Also remind participants ticked, the participants). Once the deadline passes it sends one Overdue alert the same way. Task reminders are not emailed.

Task saved with a deadline Due soon push + bell, once Deadline the due time Overdue push + bell, once time reminder offset (default 1 day) next hourly check Offset: No reminder · At deadline · 1 hour · 3 hours · 1 day · 2 days · 1 week before To the assignee (the owner if none), plus participants if “Also remind participants” is on. New deadline re-arms both · Reopen re-arms Overdue · Completed and Cancelled stay silent
FlowTwo alerts per task, each sent once: "due soon" at the offset, "overdue" just after the deadline. Change the deadline and both are armed again; reopen a completed task and the overdue alert can fire again. Completed and Cancelled tasks never ping.
OffsetMeaning
1 day beforeThe default for a new task.
At deadlineRemind exactly at the deadline.
1 hour · 3 hours · 2 days · 1 week beforeRemind that far ahead.
No reminderNo "due soon" nudge — a silent due date (the overdue alert still fires).

Recurrence

A task can Repeat Daily, Weekly or Monthly, optionally until an Ends on date. A nightly run creates the next copy ahead of its due date — early enough for its “due soon” reminder (a day before, by default) — so a "Weekly stock count" or "Month-end close checklist" reappears without anyone re-creating it. Each copy is a fresh Pending task with its own number and history; it keeps the title, description, assignee, priority, reminder setting, participants, project/milestone and linked record, and its checklist starts unticked.

Original task Repeat: Weekly Nightly run about 1 AM New copy Pending, new TK no. Next due +1 day/week/month checked again every night due within a day + reminder? SERIES STOPS WHEN Stop repeating (task menu) · the “Ends on” date passes · the original is cancelled or deleted NOT A TRIGGER Completing a copy (or the original) — copies arrive on schedule whether or not the last one is done.
FlowRepeats run on the calendar, not on completion. Finishing this week's copy doesn't bring next week's forward, and leaving it open doesn't hold it back. To end the series use Stop repeating on the original task (copies already made are kept), set an end date, or cancel the original.
Two background jobs run this

Reminders are an hourly check; repeats are a nightly run (about 1 AM). Both run on Deetzo's servers — they fire whether or not anyone has the app open, so a reminder still reaches your phone as a push overnight.

05

Templates & views

Start faster; see it your way.

Task templates

A task template pre-fills a new task: a default priority, a deadline offset (e.g. "due 7 days out"), a starter checklist, default participants and an assignee. Turn a repeatable job — onboarding a customer, closing a month — into a one-click task with its steps already listed.

Five ways to look at your tasks

ViewBest for
My DayA focused, today-first list of what's yours and due.
ListThe full sortable/filterable table (screenshot in §00).
BoardA Kanban by status — drag between Pending / In Progress / In Review / Completed.
DeadlineA time-ordered view to catch what's slipping.
DashboardRoll-up charts and counts across your tasks.

Filters — status chips, a label filter, assignee — combine with any view, and your saved views persist per user, so your grouping and columns come back next time.

06

Collaboration — discussions & @mentions

A comment thread on any record, with mentions that reach people.

Collaboration is a single, app-wide comment system. Any of these record types can carry a discussion thread, embedded right on the record:

lead· task· quote· sales order· invoice· purchase order· work order

Type @ and pick a teammate to mention them — that drops the thread into their Inbox and notifies them (§07). Mentions are how you pull the right person into a specific record without leaving it.

Comment on a recordYou write on an invoice's thread and @mention a colleague
Their InboxThe comment appears under that record in their Inbox, marked unread
Push, bell + emailDeetzo notifies them, unless they've switched mention alerts off in Notification settings
They reply in-threadReply lands back on the same record — context never leaves it
Who can comment — the viewPerm gate

Reading a thread is open to any active team member, but posting a comment is gated by the record's own view permission: you must be able to see that kind of record to talk on it. A CRM thread needs canViewCrm, a sales thread canViewSales, a purchasing thread canViewPurchases, a work-order thread canManageWorkOrders. Collaboration inherits the module's access — it never widens it.

07

The Inbox & notifications

Everything aimed at you, in one place — and the pings that get you there.

The Inbox

The Inbox (/inbox) collects the comments where you were @mentioned, grouped by the record they happened on. Replies you weren't mentioned in, and tasks assigned to you, don't land here — tasks go to your Tasks workspace and the bell. Opening an item takes you straight to that thread — you can reply without loading the whole record. Unread tracking is per-user: Deetzo remembers what you've seen, so only genuinely new activity is highlighted, and opening a thread marks it read.

When it's quiet

An empty Inbox reads "You're all caught up" — no mentions or thread activity waiting on you. That's the goal state, not an error.

Notifications

What reaches you, and how:

EventWhoInboxBellPushEmail
@mention in a threadeach person mentioned (not yourself)YesYesYesYes
Task assignedthe new assignee (not when you assign yourself)—YesYesYes
Task due soon / overdueassignee, plus participants if chosen—YesYes—
Task completedthe business owner and the task's creator—adminsYes—

Each person can turn off Notify me when I'm @mentioned (push + bell) and Email me when I'm @mentioned separately in Notification settings. The push/email switches for the task events are set for the whole business in the same screen.

No inbound-email automation

Collaboration is outbound — Deetzo sends you email/push about activity. Replying to those emails does not post back into a thread, and there's no "email an address to create a task" inbound automation. Comments and tasks are created inside the app.

08

Quick reference

The essentials.

ConceptValues
Routes/tasks · /inbox (task detail/create + discussion threads are embedded, no URL)
Task statuspending · inProgress · onHold · inReview · completed · cancelled · reOpen
Prioritylow · medium · high
ViewsMy Day · List · Board · Deadline · Dashboard
Reminder offsetNo reminder · At deadline · 1h · 3h · 1 day (default) · 2 days · 1 week before; plus one overdue alert
RepeatDaily · Weekly · Monthly, optional Ends on date; copies are made on schedule, not on completion
Comment record typeslead · task · quote · salesOrder · invoice · purchaseOrder · workOrder
Comment gatecanViewCrm · canViewSales · canViewPurchases · canManageWorkOrders per record type
Route guardNone on /tasks / /inbox — access is scoped by data + Firestore rules, not the route
Background jobsReminder check (hourly) · repeating-task copies (nightly, ~1 AM) · mention, task-assigned and task-completed alerts (on write)
The one mental model to keep

The task is portable, the thread is anchored. A task can live standalone, in a project, or pinned to any record — and follow you across the KPI tiles and views. A discussion thread stays put on its record; @mentions and the Inbox are how it reaches out to a person. Together they turn silent records into a place your team actually works.