Remove a Selected Google Drive Knowledge File
Confirm why a Drive source should be removed, map dependent answers, update the selection, and retest before relying on the change.

Remove the source, then check the consequence
Removing a selected Drive file changes the material available to an assistant, so treat it as a knowledge decision rather than a cleanup click. First identify why the file should no longer be used. It may be obsolete, duplicated, outside the assistant's audience, or superseded by an approved version. Confirm that the owner agrees with the change and identify which customer questions depend on the document. Resonoon's Google Drive knowledge flow offers a visible Remove operation for a selected item; your team remains responsible for deciding whether removal is appropriate.
Suppose a shop has replaced its delivery policy. The old document may still answer questions about regions and timeframes that the new policy handles differently. Removing it without checking dependencies could leave the assistant without a source for those questions. Keeping both can also expose conflicting guidance. Compare the relevant passages, confirm which version is canonical with the policy owner, and make a list of affected questions before changing the selection.
Review the selected list carefully
Open the source management flow and inspect the selected files. Verify the exact item by its displayed name and, where the interface provides enough context, its identity. Similar titles can make a mistaken removal difficult to notice. Use Remove on the intended item and confirm that the selection list updates. That visible change is evidence that the selection changed; it is not by itself proof that every answer was refreshed or that a replacement source is correct.
Adding Drive files merges them with the current selection. Therefore, do not assume that choosing a replacement automatically removes the old file. Inspect the resulting list after adding, and explicitly remove the superseded source when the owner has approved that decision. If an item is still needed for another assistant task, consider the audience and source boundaries before removing it from that assistant's selection. Check the assistant's selected-file list to confirm the removal; manage the original file separately in Google Drive if it also needs changing. The product operation concerns its selected knowledge source.
After the selection changes, review the source's visible status and any displayed errors. Knowledge-source management includes save, sync, and delete operations, but use only controls presented for the source and note what the interface reports. Record the status as displayed and retest the affected questions before relying on the changed selection for customer answers. Connecting an account is separate from selecting and saving files, and a selection change is separate from verifying answers.
Map the answers that may change
Before removal, make a short dependency list: customer question, old passage, replacement passage if available, and expected outcome. For example, record questions about delivery to a remote region, estimated time, and orders already in transit. These may depend on different sections. A new general policy may not cover an exception stated only in the old file. Ask the policy owner whether that exception remains valid rather than preserving stale text just in case.
Once the selected list reflects the approved sources, run the same questions through the assistant test experience. Compare the new answers with the canonical material. Include a question that should still be answered, one whose answer changed, and one that should now be treated as unsupported. If the assistant continues to state the old rule, inspect the source list and displayed sync details before editing role instructions. If the answer is missing, determine whether the replacement document actually contains it. This separates a source problem from a response problem.
Do not ask the assistant to decide which conflicting version should survive. The policy owner makes that decision, and a reviewer records it. Keep the prompts and expected answers in a team-owned record. Use this record to trace which questions were checked after the removal and which still need a replacement source or human answer. Reviewers must identify affected questions themselves.
Close the change with an owner
A removal is complete only when the selected source list, the approved replacement, and the answer checks agree. Assign an owner to monitor changes to the underlying Drive document and define when another review is due. A policy revision, new product range, or recurring customer question can be a trigger. Keep obsolete versions out of the active selection, but retain records according to company policy so reviewers can explain when and why the source changed.
When a connected source is edited, do not promise that its new wording appears immediately. Check the available source status and last-synced information, use a visible sync operation where appropriate, and retest affected questions. If the update is time-sensitive, ensure the team has a customer-safe response until the source and answers are verified. Agree who will handle those questions while the checks are pending and what wording staff should use.
Removing a source responsibly means knowing what it contains, why it is no longer valid, and what answers might change. Confirm the owner decision, update the selection, inspect the visible result, and rerun concrete questions. For context on the assistant's customer-facing role, read about the AI chatbot widget.