Kimi Work connects Notion and Lark documents: ask questions beside the source

On September 30, 2026, Kimi Work 3.2.15 updated its collaboration entry points for Notion and Lark documents. The official release notes describe three changes: quickly opening documents from the home sidebar; displaying documents created through plugins as artifact cards; and asking questions about a page and editing annotations in the built-in browser.

This matters most to people who work with plans, meeting notes or project material. A document does not first have to become a long passage pasted into a chat before you can read it with AI. The source page, questions and annotations can stay connected to the same document.

The announcement's description of human–AI coediting is not an unlimited promise about document operations. It explicitly covers these entry points, page Q&A and annotation support. Whether you can open or change a document still depends on your access to it.

Less copying, and one less stale copy to manage

Suppose your team's event plan is in Lark and you want to find missing dates and owners. Your usual routine might be to select everything, paste it into AI, read the answer and locate each point back in the original. If the document changes later, the copy in chat may not follow it. Opening the source in Kimi Work and asking about the page keeps verification close to reading. This reduces material handling; it does not guarantee correct answers or real-time awareness of every document change.

Turn “fix it for me” into a review you can check

For a plan that several people have contributed to, you can first ask AI to identify gaps, then inspect the original passages and add annotations yourself. A limited review can preserve the team's existing wording and responsibilities more readily than immediately rewriting the whole document. Annotations raise questions to confirm; the responsible person still makes the decision.

Good first tasks include finding action items without an owner or date, explaining difficult project background, and listing statements that appear inconsistent. Page Q&A does not establish that AI has automatically read every attachment, link or the entire workspace.

Use a Kimi Work version that includes the feature and prepare a Notion or Lark document you can access. Kimi Work's overview describes its focus on everyday knowledge work; the plugin center connects external applications and extends conversations. If a connection is needed, grant only the access this task requires.

1. Start with an existing document. Open the target Notion or Lark document from the home sidebar and confirm that the built-in browser shows the intended material. Resolve login or access problems first rather than asking AI to guess what is there.
2. Ask a verifiable question. Define the scope in page Q&A. For example: “Check only the activity-preparation list on this page. List tasks without an owner or due date and quote the relevant sentence. Mark missing information as unspecified; do not invent names or dates.” This is a suggested prompt, not a vendor demonstration result.
3. Check the original sentences. A useful output is a short table of source text, missing information and who needs to confirm it. Compare each row with the page, particularly whether AI has turned a suggestion into an agreed arrangement.
4. Hand over the questions manually. Copy the checked list and send it to the document owner through the team's usual communication channel. This is a manual collaboration suggestion; it does not depend on Kimi writing annotations back to Notion or Lark or on other people seeing annotations inside Kimi. Recheck the relevant passages after the owner changes the source. Do not keep treating an earlier answer as current.

If you created a document through a plugin, its artifact card can also take you back to it. Begin with one page and one question. Confirm how the entry point, answer and source connect before moving to longer material.