Keep the context with the work.

01 / COLLABORATION

Discuss the subject people are working on

Comments belong to a record, process or task rather than a disconnected conversation. This gives the next person a place to understand clarification, supporting context and the reasoning shared during a handover. The subject’s access boundary remains important: participation follows authorization, not possession of a public link.

Use comments for operational context and keep authoritative business values in structured fields. A comment can explain a decision, but it should not become an informal substitute for required data capture or an authorized task action. This distinction keeps subsequent routing and reporting understandable.

02 / COLLABORATION

Attach supporting files without making them public

Private attachments connect supporting documents to the subject of the work. File delivery is controlled so an authorized user can obtain the file through the application. Storage and application access are separate concerns from the convenience of uploading a document.

An evaluation should include an authorized download and an attempted access outside the intended scope. Consider what information your team should attach and how it will handle downloaded copies. The platform’s private delivery boundary does not replace the organization’s policies for information after it leaves the application.

03 / COLLABORATION

Read the history of work and change

Activity history provides context for what happened around a subject. Audit records serve the governance and review needs of the platform. Together with process execution history, these views help people distinguish the current work state from the discussion and changes that led to it.

During evaluation, hand a task between eligible people with a comment and supporting attachment. Inspect the task, associated record and activity afterward. Confirm that a person receiving the work can locate the relevant context without being given broader administrative access.

• Associate discussion with its business subject.
• Use private files for relevant supporting material.
• Review effective access before sharing context.
• Inspect activity alongside process and audit history.