Select Relevant Google Drive Documents for an Assistant
Choose a focused set of approved Drive files for one assistant task, confirm the selection, and test what the selected sources can answer.

Select for one assistant task
A connected Drive account can contain far more information than a single assistant should use. Choosing a focused set reduces irrelevant material and makes reviews easier. Start by writing down the assistant's audience, its job, and the questions it must answer. Then identify the specific files that support those questions. Resonoon's Google Docs knowledge flow uses Google Drive Picker; connecting the account alone imports nothing. A non-empty selection must be confirmed to start import and save the selection.
Imagine an assistant that explains delivery and returns for an online shop. It may need the current delivery page and approved return policy. It probably does not need a staff rota, draft campaign calendar, or wholesale agreement. Those documents may be accessible from the same account, but accessibility is not relevance. The business owner should decide whether a source is approved for this audience. Keep that decision in a team-owned record if several people maintain the files.
Use questions to filter files
For each candidate document, ask what exact customer question it supports. “Where can a customer find the delivery estimate?” is more useful than “Does this seem related to orders?” Note the answer passage and whether the document includes conditions such as location, item type, or date. If a file contains both useful policy and unrelated internal material, consider whether an approved, focused document is available. Do not rewrite or split authoritative wording in a way that changes its meaning.
Check for duplicate names and versions. A file labelled “returns final” may not be the approved policy, and a recent modified date does not prove that the owner approved its contents. Compare the relevant passage, approval context, and effective date with the canonical source. If you cannot tell which version is current, ask the policy owner before selection. Do not resolve the conflict by importing both and expecting the assistant to pick correctly.
For each selected item, capture its title and the reason it belongs. This simple list supports later review when a question is answered incorrectly or a policy changes. Keep the list in your shared source register so another reviewer can trace the reasons for including each document. The product's file picker controls which Drive files are selected; your team's notes explain why.
Confirm a non-empty selection
Browse Drive, select only the files needed for the task, and inspect the selection before confirming. A selection is meaningful only if it contains the intended documents. Confirming a non-empty selection starts the import and saves it. Closing or canceling without selecting and confirming should not be treated as an import. If you are unsure, return to the source management view and check the selected items shown there.
Use a simple test for the no-selection case. Open the selection flow, make no selection, and exit without confirmation. Then inspect the source list. The expected result is that no new Drive material was imported from that attempt. This is a useful onboarding check because people often assume that authorizing the account did the work. Keep it separate from testing a successful import, where you confirm a known document and then inspect the displayed status or errors.
A small selection is not automatically a good selection. Confirm that every file has the intended audience, that its content is approved, and that it does not conflict with another chosen source. If a customer-facing assistant should not use an internal procedure, leave that procedure out even if it answers a similar question. When the business cannot yet identify a canonical answer, pause the selection and resolve the policy decision first.
Test coverage and maintain ownership
After confirming, test a few questions tied to the selected documents. Include a direct question, a condition or exception, and a question for which the chosen files do not provide an answer. Compare the responses with the exact passages, including any qualifications. If the assistant gives an answer absent from the chosen source, investigate the material and the response rather than assuming the selection was successful just because it appears in the interface.
For the delivery example, test an ordinary delivery estimate, a regional exception if one is documented, and a question about wholesale delivery if that agreement was deliberately excluded. The expected behavior for the last question should be written down before testing. It might be a request for clarification or a statement that the available source does not cover the subject. Do not ask the assistant to invent a rule from a neighboring policy.
Assign someone to review the selection when its purpose changes or a source is replaced. When adding Drive files, the selection is merged with the existing selection, so inspect the resulting list instead of assuming the new choice replaced everything. If a file is no longer appropriate, use the visible Remove operation and review dependent answers. The source-management interface includes save, sync, and delete operations; check its displayed status and errors after changes. Do not promise immediate propagation from an edited document. Learn more about the AI chatbot widget.
A focused selection is a business decision supported by a visible import workflow. By connecting the account, selecting only relevant approved files, confirming a non-empty set, and testing representative questions, a team can explain both what the assistant may rely on and what remains outside its evidence.