Pick up the work. Without starting over.

A Project groups related research conversations and human-authored Updates inside a team workspace. It helps colleagues find the work behind a conclusion and continue it. Access to that work remains governed by the organisation’s roles and permissions; grouping it in a Project does not make it accessible to everyone.

A person writes a short headline and takeaway, then links one exact research answer from the same Project. The Update keeps the Card versions associated with that answer. It is a deliberate handover, not an automatically generated activity feed or an approval.

A proposed revision stays distinct from the approved guidance while authorised people review it. Colleagues can inspect the change, its author, its reason and its approval before using the new version. Earlier answers and linked Updates keep the exact Card versions they used. Your team can therefore distinguish the current agreement from the basis of earlier work, instead of guessing who changed what or which decision a colleague relied on. A new conversation uses the relevant context selected for it; existing answers are not silently rewritten.

No. Sharing an Update does not grant permission to open a private Card. When eligible personal context contributed to a team answer, colleagues receive a generic disclosure rather than the private Card’s identity or values. Authors should also check the text they choose to publish.

Projects organise the work: conversations and Updates. Cards preserve reusable company knowledge with sources, relationships and version history. A Card can support work across Projects, subject to access and review. An Update does not automatically become a Card.

Your organisation defines roles and assigns permissions to them. These govern who can access knowledge, contribute changes, review and approve them, or manage access. Holding one permission does not automatically grant the others. Role assignments determine each person’s authority; job titles in the example are illustrative, not a fixed role catalogue. AI output and Project Updates do not override those permissions or approve changes on their own.

People authorised to manage access can revoke a colleague’s access or change their assigned roles. Company-owned Cards, Project conversations and Updates remain available to permitted colleagues under the applicable retention rules. Personal Cards remain private. A handover preserves what was actually saved and shared; it cannot preserve unrecorded expertise.

This page explains the intended collaboration workflow using an example. It does not create a workspace, publish an Update or run research. Access is by application; submitting a request does not create an immediate account or guarantee capability availability.