On this page
1. Match the information to its destination
| Destination | Useful content | Keep out of the example |
|---|---|---|
| Client job document request | The specific document needed for the engagement, in its intended request area. | Unrelated client files or a different person’s records. |
| Routine message | A clear question, date range or next step. | Full tax returns, taxpayer IDs or bank details when a simple question will do. |
| Support screenshot | Relevant control, error text and enough context to locate the issue. | Passwords, codes, unrelated records and account details. |
| Community or teaching example | Fictional scenario and a general question. | Identifiable client facts or copied financial records. |
A familiar brand or workspace does not make every destination appropriate for every file. Confirm the recipient and purpose before attaching or sharing.
2. Prepare a focused support screenshot
- Capture only the relevant panel or error. Close unrelated windows and tabs first.
- Remove names, email addresses, phone numbers, street addresses and client identifiers that are not needed.
- Remove taxpayer IDs, bank/payment details, passwords, verification and recovery codes.
- Check document previews, browser tabs, the address bar and background notifications.
- Open the final exported image and inspect it at full size before sending.
Use solid redaction for information that must be removed; a translucent highlight or light blur can leave text readable. Check the exported file itself, not only the editor view.
3. Replace client facts with a fictional example
“A bookkeeping client needs September transactions reconciled. Which records should I request before confirming the scope?”
This explains the teaching problem without naming a person, revealing account balances or attaching a real statement. Label invented examples as fictional, and avoid combining so many distinctive facts that a real person is still recognizable.
4. Check the actual file and recipient
Before sending, reopen the attachment, confirm the recipient or channel and read the message with the attachment included. Check that filenames and extra pages do not reveal details you removed from the visible first page.
For client files, confirm the correct job and request. For a support issue, include the exact error and action rather than adding an entire client file “just in case.” If support needs more, clarify the item and intended channel first.
5. Respond promptly to a mistaken share
If you notice the wrong file or recipient, stop further sharing. Use any available removal control, then contact the appropriate support or responsible person with what happened, where it went and when. Follow your organization’s incident process.
Do not assume deleting a message removes downloaded copies or ends the issue. Keep a factual record of the actions taken without spreading the sensitive attachment further.
Common questions
Can I use a real client screenshot in a community example?
Prefer a fictional example. Community teaching usually does not need identifiable client facts or financial records.
Is cropping enough?
Only if the remaining image contains no unnecessary identifying or sensitive information. Inspect the whole export, including filenames, tabs, notifications and document previews.
Should I send support my password or verification code?
No. Describe the tool, action and error. Keep passwords, one-time codes and recovery information out of the message and screenshot.
Does deleting a message guarantee no one has the file?
No. Do not assume removal reverses access or downloads. Follow up through the appropriate support or incident process.
Learn more
Prepare document requests and organize your files
Separate client requests from your own library and ask for clearly named records.
Read guide
Choose and preview tax organization forms
Inspect the audience, conditional questions and preview-only state before selection.
Read guide
Find account settings in each Uncle Kam tool
Locate practice and security controls without assuming settings synchronize.
Read guide