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.
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.
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.
Anatomy of a task
Everything one task can carry.
| Field | What it does |
|---|---|
| Number | TK-0001 — assigned atomically from a per-tenant counter, so numbers never collide or repeat. |
| Assignee | The one person who owns it. Reassign is a single action and is logged to the activity trail. |
| Priority | low · medium · high — a plain flag, drives sort and the KPI tiles. |
| Due date + reminder | A deadline plus a reminder offset (see §04). Overdue tasks feed the Overdue KPI. |
| Checklist | Lightweight tick-items inside the task — good for a definition-of-done that isn't worth a sub-task. |
| Sub-tasks | Child tasks (parentTaskId) — a task can break into smaller tasks that roll up to it. |
| Participants | People beyond the assignee who watch the task and can be reminded and notified. |
| Dependency | A single finish-to-start predecessor. It's advisory — Deetzo surfaces it, it does not hard-block you from starting. |
| Record link | The record the task hangs off — an invoice, quote, customer, supplier, purchase, vendor bill, or a project + milestone (§03). |
| Extras | Attachments (files or a ZIP), custom fields, labels/tags, and a recurrence rule (§04). |
The task lifecycle
Seven states — richer than "todo / done".
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.
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.
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.
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.
| Offset | Meaning |
|---|---|
| 1 day before | The default for a new task. |
| At deadline | Remind exactly at the deadline. |
| 1 hour · 3 hours · 2 days · 1 week before | Remind that far ahead. |
| No reminder | No "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.
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.
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
| View | Best for |
|---|---|
| My Day | A focused, today-first list of what's yours and due. |
| List | The full sortable/filterable table (screenshot in §00). |
| Board | A Kanban by status — drag between Pending / In Progress / In Review / Completed. |
| Deadline | A time-ordered view to catch what's slipping. |
| Dashboard | Roll-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.
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:
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.
@mention a colleagueReading 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.
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.
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:
| Event | Who | Inbox | Bell | Push | |
|---|---|---|---|---|---|
| @mention in a thread | each person mentioned (not yourself) | Yes | Yes | Yes | Yes |
| Task assigned | the new assignee (not when you assign yourself) | — | Yes | Yes | Yes |
| Task due soon / overdue | assignee, plus participants if chosen | — | Yes | Yes | — |
| Task completed | the business owner and the task's creator | — | admins | Yes | — |
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.
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.
Quick reference
The essentials.
| Concept | Values |
|---|---|
| Routes | /tasks · /inbox (task detail/create + discussion threads are embedded, no URL) |
| Task status | pending · inProgress · onHold · inReview · completed · cancelled · reOpen |
| Priority | low · medium · high |
| Views | My Day · List · Board · Deadline · Dashboard |
| Reminder offset | No reminder · At deadline · 1h · 3h · 1 day (default) · 2 days · 1 week before; plus one overdue alert |
| Repeat | Daily · Weekly · Monthly, optional Ends on date; copies are made on schedule, not on completion |
| Comment record types | lead · task · quote · salesOrder · invoice · purchaseOrder · workOrder |
| Comment gate | canViewCrm · canViewSales · canViewPurchases · canManageWorkOrders per record type |
| Route guard | None on /tasks / /inbox — access is scoped by data + Firestore rules, not the route |
| Background jobs | Reminder check (hourly) · repeating-task copies (nightly, ~1 AM) · mention, task-assigned and task-completed alerts (on write) |
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.