PlatformFeaturesPricingHelpVerify Passport
NEXPURA
AboutBook a DemoLoginStart Free Trial
PlatformFeaturesPricingHelpVerify PassportAboutBook a DemoLogin
Start Free Trial
NEXPURA

The operating system for modern jewellers.

Product

  • Platform
  • Features
  • Pricing
  • Security

Resources

  • Blog
  • The Problem
  • Help

Company

  • About
  • Contact
  • Book a Guided Demo
  • Start Free Trial

For Customers

  • Verify Passport

Legal

  • Terms
  • Privacy

© 2026 Nexpura. All rights reserved.

Built for jewellers.

Back to all docs
Documentation · Section 10

Tasks & Workflow

The internal to-do surface. Tasks live on /tasks with a My-tasks slice for the signed-in user and an All-tasks slice for owners and managers. Each task can carry a priority, a due date, an assignee, and a link to a repair, bespoke job, inventory item, or supplier — so the same surface drives both freestanding to-dos and the per-job checklist on workshop work. Three pages covering the daily flow. Workshop-specific filtering of the same task table is described under Workshop — the /tasks/workshop view is the same data filtered to linked_type IN (repair, bespoke).

01

Tasks overview

What tasks are for in the Nexpura mental model — internal to-dos for the team, optionally linked to a repair, bespoke job, inventory item, or supplier record. The /tasks board (My tasks vs All tasks), priority and status fields, the Kanban view, the workshop-tasks slice, and how task assignment fires a WhatsApp ping to the assignee.

02

Comments and attachments

Discuss a task in-thread, attach reference photos or PDF instructions, and read the activity timeline of every state change. Comments are append-only today (no edit, no delete from the UI), attachments cap at 10 MB and accept JPEG / PNG / WEBP / HEIC / PDF.

03

Task templates

A tenant-scoped library of named task shapes — title, department, priority, description — that you maintain at /settings/task-templates. Today the library is a reference list owners and managers curate; one-click apply from the new-task form is the next-step build, so the current workflow is copy-paste from the template page into the create form.