An internal answer can sound reasonable and still rely on the wrong policy, an outdated document, or information the user should never have seen. The deployment work includes deciding how the team will catch those failures and who will fix them.
Sources checked September 20, 2026. This is a review of Glean’s public documentation, not a hands-on test or customer deployment. It covers internal knowledge retrieval and answer review, not Glean’s complete agent platform. Recommendations and proposed tests below are ours; they are not verified product outcomes.
The workflow at a glance
| Layer | Documented behavior | Team decision |
|---|---|---|
| Source selection | Assistant combines company, web, and model knowledge, with query controls | Which sources belong in this workflow? |
| Permissions | Connector permissions and source-specific discovery rules affect visibility | Which users and sharing patterns need testing? |
| Content ownership | Document verification includes a verifier and review reminders | Who maintains authoritative guidance? |
| Answer review | Citations and feedback support troubleshooting | Who fixes the source, configuration, or answer? |
The sections below link each documented behavior to its source. A documented control is a starting point for evaluation, not evidence that a particular configuration passed.
Record the sources the assistant can use
Glean’s current information-access guide describes All Knowledge as the default. It combines accessible company information, web information, and model knowledge. Query toggles control company retrieval and web search; web search also depends on administrator enablement. Turning both retrieval toggles off still allows supplied chat context, and does not itself remove available write tools. Glean’s information-access guide.
Our take: record retrieval settings and action permissions separately. For a policy-answering pilot, require the reviewer to identify the authoritative internal source. A fluent general answer should not substitute for the company’s actual policy.
Test the connector’s specific permission rules
Glean says search visibility uses identity and permission information collected alongside content and activity. Search permissions overview.
The Google Drive connector adds a more specific discovery model for broadly shared documents. Its documentation describes conditions involving prior access, searchability settings, Slack link sharing, and pinned audiences. The Slack-sharing behavior is optional. These details concern discovery of documents already shared broadly; they should not be read as a general bypass of restricted-file permissions. Google Drive permission rules.
Proposed test: use synthetic documents and two test identities. Check a restricted file, a domain-shared file, and a broadly shared link. Change access, then record when retrieval reflects the change. Agree with your administrator on the acceptable delay and the response if restricted material appears. This article establishes no revocation-time guarantee.
Give freshness an owner
Glean’s verification feature records a user’s approval that a document is current and accurate. Results can show the verifier and verification date; owners can set reminders to review it again. How document verification works.
Our take: distinguish a fresh index from correct content. A recently indexed policy can still be obsolete. Assign an owner to the important sources and ask them to resolve contradictory guidance before treating the answers as dependable.
Proposed test: ask the same policy question against a current source and an older conflicting one. Record which sources appear, whether the answer recognizes the conflict, and how a reviewer reaches the accountable owner. Repeat after correcting the source. Keep both observations rather than overwriting the failure.
Route an incorrect answer to the right person
Glean’s troubleshooting guidance starts with checking citations against the original document. It distinguishes missing access or indexing from answer-quality problems, and describes submitting feedback with context. Feedback is reviewed; it does not automatically retrain answers or guarantee an immediate correction. Troubleshoot answer quality.
Our proposed operating split: the document owner fixes obsolete guidance; the connector administrator investigates missing or unexpected access; the pilot owner records answer failures and decides whether to pause the workflow. Product feedback supplements that process. It does not replace an internal owner.
Bring five cases to the pilot review
These are proposed tests, not results from Glean:
- Known answer: an approved, current source contains the answer. Check support for every consequential claim.
- Restricted answer: only another test user can access the source. Check the answer, citations, and previews for exposure.
- Changed access: revoke access to a synthetic document. Measure propagation and follow the agreed response if it exceeds the boundary.
- Conflicting sources: current and obsolete guidance disagree. Check whether the reader can identify the authoritative source.
- Missing evidence: no approved source supports an answer. Check whether the response makes that limitation clear and directs the user to an owner.
Use the pilot evaluation worksheet to record expected behavior, actual results, review effort, and unresolved failures. Add the connector, content owner, and next review date to your AI stack inventory.
What we’d watch
Repeat the relevant tests when source sharing, connector configuration, or assistant settings change. Before expanding the pilot, review unresolved access failures individually and confirm that someone owns the sources people rely on most.