Tasks and support

Availability: Onboarding Tasks, conversations, attachments and the notification inbox are built locally; Dev release checks remain open. The sample Support page does not contact anyone.

Tasks hold work that a team needs to review. A task has a description, state, messages and attachments. Available actions depend on your access and who created the task. Drafts stay private. The server decides which next states you can choose.

Task approval concerns that task. It does not approve a letter for printing or delivery.

Sent messages keep their author and time; they cannot be edited or removed. Access and task state can limit attachment changes. If a save reports that the task changed, reload it before trying again. If an upload loses its reply, check the attachment list before adding it again.

A saved change can create a notice or queue an email. That does not prove the email reached its reader. Removed access can hide an older notice or task link.

Staff-only notes, call booking, recordings and AI summaries are not real support tools in the new portal. Do not put passwords or donor files into the sample workspace. When asking for help, give the screen name, action and error instead.