Good knowledge transfer explains how to continue the work without turning the handover into a store of secrets. Use your organization's information-sharing rules when deciding what to include.
Include the minimum useful context
Document responsibilities, procedures, relevant work contacts, decisions, and approved source links. Explain what a resource is for rather than copying an entire sensitive record into an answer.
Do not add passwords, API keys, recovery codes, private customer records that are not needed, or unrelated employee information. Describe how the successor requests access through the approved process. For a leave-related case, focus on coverage needs rather than private personal circumstances.
Choose participants deliberately
Check email addresses before sending invitations or collection links. Add people who need to contribute to or review the handover. Organization roles and case roles have different purposes; see users and roles.
Check AI-generated content
Review generated questions, summaries, and documents for accuracy and unnecessary sensitive detail. AI output can make incorrect assumptions. Correct critical facts with the people who know the work before relying on the result.
Handle exports with the same care
Downloaded PDF, Word, and Markdown files are separate copies. Keep them in approved storage, share them only with the intended recipients, and follow your organization's retention policy.
If sensitive information was included by mistake, involve your organization's responsible administrator and contact Flamekeeper for help. Do not copy the sensitive content into the support message; explain the issue and the affected area first.