Client tracking
Use projects for client engagements, tasks for follow-ups and comments for internal delivery notes.
Track an engagementLink to section
Use an internal workspace to coordinate a client delivery. The example starts with Northstar — website launch, a scope description and an internal owner. It uses the included Projects module and requires no new schema.
| Your vocabulary | Existing model | Example |
|---|---|---|
| Client engagement | Project name and description | Northstar — website launch |
| Internal owner | Project responsible membership | A member of your workspace |
| Follow-up | Task title, description, assignee and due date | Confirm the launch copy |
| Delivery note | Task comment | Copy reviewed; two wording changes remain. |
Try the workflowLink to section
Create the engagementLink to section
Open Projects → Create project, enter the name and scope, choose a responsible member and save. Open its detail page.
Plan the follow-upsLink to section
Add Confirm the launch copy, Review the delivery and Prepare the handover as tasks. Give each a responsible member and calendar due date.
Work and verify persistenceLink to section
Move the first task from TODO to IN_PROGRESS, post the internal note and
reload. Confirm that its status, assignee, date and discussion persist.
Complete and retain the engagementLink to section
Mark completed follow-ups DONE, then update the project's own status
separately. Archive it to pause task/comment edits; restore before editing
again. Deleting the project removes its tasks and comments.
Internal records share workspace access
All active workspace members can see these client records and notes. A project does not isolate one client's data from another. Decide the customer/workspace model and server permissions before inviting external clients or building a portal.
Adapt the presentationLink to section
The shipped docs/recipes/client-tracking.md identifies the existing source
entry points and includes a scoped assistant prompt. Start with the project
detail page, config/product.ts navigation and the English/French UI copy.
Keep persisted status codes and workspace service guards. Use page-specific
engagement labels if the application also contains other project workflows.
Check before adoptingLink to section
- A MEMBER can create a follow-up and post a note; assignment does not limit editing to its named owner.
- Another workspace's project, task, comment or assignee ID is rejected.
- Reload and language changes retain user-authored names and notes.
- Archive blocks task/comment writes until restored; it is not permanent retention.
A contacts directory, customer account history, customer-specific access and billing per client are extensions to design. The baseline does not add them.