Feedback data handling
When a user provides in-product feedback with an upvote ( Helpful) or downvote ( Not helpful) per response, Glean records the rating and a scrubbed set of supporting fields. Learn exactly which fields leave your deployment, how to restrict them, and who can access them. Use this information to complete a privacy or compliance review of the feedback feature.
Understand feedback destinations
Every feedback submission can go to two places: to Glean, and to your own company.
Each destination has its own toggle and shows its current state in the Admin console:
| Destination | Toggle | When on | Default |
|---|---|---|---|
| Glean | Allow Glean to receive in-product user feedback | When a submission files a Glean support ticket, the ticket carries:
| On |
| Your company | Allow (your company name) to receive in-product user feedback | Glean emails the following to the feedback addresses you specify:
| Off |
Configure feedback destinations
An Admin or Super Admin configures both destinations on the Help settings page in the Admin console, under Feedback. See Admin roles.
If you turn on company delivery without a primary feedback email address, Advanced preferences opens automatically. Enter the required primary address and click Save to enable company delivery. Other destination-toggle changes save immediately. Turning one destination off has no effect on the other.
When the Glean destination is on for a surface, these rules decide whether a submission files a Glean support ticket:
| Action | Files ticket | Does not file ticket |
|---|---|---|
| Downvote with a reason category or a comment | ✅ | |
| Upvote with a comment | ✅ | |
| Upvote with no comment | ✅ | |
| Click a thumbs-up or thumbs-down icon without submitting the feedback form | ✅ |
Turning the Glean toggle off stops the Glean support ticket. It does not stop the scrubbed feedback analytics or the feedback events in Glean Customer Event logs, which Glean records regardless of feedback-destination settings.
Feedback emails sent to your configured addresses are the company destination, not the Glean destination. The conversation content included in an email depends on where the feedback originated. See Feedback originating in Slack for Slack-specific transcript boundaries.
Glean sends feedback to the configured destinations when the user submits, so you cannot approve feedback before a destination receives it. To review feedback internally before a Glean support ticket is filed, turn off the Glean destination and route feedback to your own addresses or ticketing system. Scrubbed feedback analytics are still recorded.
Control feedback destination per surface
Click Advanced preferences to see the General, Chat & Agents, and Search rows. The Recipients column has checkboxes labeled with Glean and your company name. The email fields control where company feedback is sent.
If you clear the Glean checkbox for a surface, that surface files no Glean support ticket while other selected surfaces still do. This does not stop the scrubbed feedback analytics or the feedback events in Glean Customer Event logs. Click Save to apply changes made in Advanced preferences.
You can only edit the per-surface checkboxes when the corresponding parent toggle is on. You cannot exclude general feedback per surface.
Route feedback notifications to an email address
To set where feedback notifications go:
- Open Help settings in the Admin console and expand Feedback.
- Turn on Allow (your company name) to receive in-product user feedback. Open Advanced preferences if it does not open automatically.
- Enter the required Primary (your company name) email for routing feedback.
- Select Use for all types of feedback to use the primary address for every feedback type. To use separate addresses for Chat & Agents or Search, clear that option and enter an address in the corresponding row.
- In Recipients, select the company-name checkbox in the Chat & Agents or Search row for each type you want to receive. General follows the company toggle and cannot be excluded separately.
- Click Save.
Use a single organization-approved address or mailing-list alias in each email field. Choose recipients who are authorized to review the feedback and conversation content.
Glean recommends configuring a separate alias to assist in routing. You may also want to automatically ingest this feedback into a ticketing system like Jira, Zendesk, or ServiceNow.
Feedback originating in Slack
Glean can email negative feedback submitted on answers in Slack to the recipients configured for Chat & Agents. To enable these company notifications:
- Open Help settings in the Admin console and expand Feedback.
- Turn on Allow (your company name) to receive in-product user feedback. Open Advanced preferences if it does not open automatically.
- Enter the required Primary (your company name) email for routing feedback. To use it across all feedback types, select Use for all types of feedback. For a separate Chat & Agents address, clear that option and enter an address in that row.
- In the Chat & Agents row, select the company-name checkbox under Recipients.
- Click Save.
Slack feedback uses the Chat & Agents address. If that address is not set, Glean checks an existing legacy Chat feedback address, then the primary feedback address. If none is configured, no email is sent.
The email includes the submitter's email address, the rating, any submitted reason or comment, and the available question and downvoted answer. For agent feedback, it also includes the agent name. Slack-specific context can include the feedback surface, the conversation type (with the channel name for public channels), and a message link. The transcript content depends on where the feedback originated.
| Slack conversation | Conversation content in the company email |
|---|---|
| One-to-one direct message with Glean | The downvoted exchange and available earlier messages, ending at the downvoted answer. The transcript contains at most 50 message entries, with the oldest entries omitted when it exceeds that limit. |
| Public or private channel | Only the question and downvoted answer, not the channel's conversation history |
| Group direct message | Only the question and downvoted answer, not the group conversation history |
If earlier direct-message history cannot be retrieved, the email retains the available downvoted exchange. A Slack message link is included only when Glean can obtain it. The email transcript may not preserve rich formatting such as tables and code blocks.
Turning off delivery to Glean does not turn off company feedback emails. Company emails can still contain the question, answer, and available conversation context. Configure the company destination separately to stop those emails. The support feedback payload, scrubbed feedback analytics, and feedback events in Glean Customer Event logs are separate records with different content and controls.
If Slack feedback emails do not arrive, check the following:
- Confirm that the company toggle is on and the company-name checkbox is selected in the Chat & Agents row.
- Check the recipient address and click Save after changing Advanced preferences.
- Confirm that the user submitted the feedback form. Clicking a thumbs-down control alone does not confirm email delivery.
Delivery also requires manual feedback for Glean in Slack and Slack feedback emails to be enabled in your deployment. If the checks pass but emails still do not arrive, contact Glean Support to check feature availability, manual-feedback controls, and the email-delivery service.
Submit feedback in Slack
To submit negative feedback, click Not helpful or the thumbs-down icon on a Glean answer. In Share feedback, select a reason, add an optional comment in Tell us more, and click Submit. For a Slack-published agent, the dialog also explains how feedback may be shared.

Feedback form for a Slack-published agent. The example comment is redacted.
Glean then displays an acknowledgement in Slack. This confirms submission, not delivery to the configured email recipients.

Slack acknowledges the submitted feedback.
Forward feedback emails to Slack
This routes feedback notification emails into Slack. It is separate from feedback submitted on Glean answers in Slack.
To automatically forward feedback emails to a Slack channel, for example #glean-chat-feedback, first generate a destination email address for that channel:
- Open the Channel Information page for a channel you own and click the Integrations tab.
- Click Send emails to this channel, then Get Email Address.
- Raise a ticket with Glean Support to associate the Slack domain from this email, for example company.slack.com, with your Glean instance.
- Copy the Slack email address into the Feedback section of Glean Settings and click Save.
Have Glean Support associate the Slack email domain with your organization before using the channel address for feedback.
Review who can access agent feedback
Workspace admins can review feedback across all agents in their workspace. Agent builders can review feedback only for the agents they built.
| Audience | Access scope | Purpose |
|---|---|---|
| Glean | Agent feedback, plus a session debugger link for support | To review issues and diagnose problems. |
| Workspace admins | All agent feedback in the workspace | To monitor feedback and investigate quality or usage issues across agents. |
| Agent builder | Only feedback for the agents they built | To diagnose agent-specific problems and improve those agents over time. |
This access is separate from email-based routing, which only controls where feedback notifications are sent. The sharing rules apply to agent feedback and do not change feedback routing for standard chat and search.
Users see a disclosure in the feedback modal for agent chats, explaining that their chat and feedback may be shared with Glean, their admins, and the agent's builder. See User feedback.
Review what Glean receives
The following table describes what Glean can access when you configure Glean as a feedback destination:
| Record | When Glean receives it | Glean access | Retention |
|---|---|---|---|
| Complete feedback record | By default, Glean does not receive the complete feedback record. The record, including the conversation context, stays in your own cloud storage. | No | 270 days by default. If your admin sets a chat retention period, chat feedback and chat message records in the complete feedback record follow that period instead. See Chat History. |
| Feedback logs | By default, Glean does not receive feedback logs. The logs stay in your own deployment project. | No | 270 days |
| Support feedback payload | Only when the Glean destination is on | Yes | 270 days |
| Scrubbed feedback analytics | On every submission, whatever the destination settings, on a route separate from the support payload | Yes | Contact Glean Support for retention details. |
| Glean Customer Event feedback events, copy in your deployment | Glean does not receive this copy. It stays in the glean-customer-event log in your own deployment project. | No | 270 days by default. See Glean customer event logs. |
| Glean Customer Event feedback events, scrubbed copy | On eligible chat and search feedback, regardless of feedback-destination settings | Yes | Contact Glean Support for retention details. |
| Downvote analysis output | Only on deployments that use the Glean Universal Model Key. Customer Key deployments do not run downvote learning. | Yes | 90 days |
Glean engineers can access the complete feedback record and feedback logs only through an approved debug operation. See Understand how Glean engineers access conversation content.
The support feedback payload
This record drives the Glean support ticket. When the Glean destination is on, Glean receives:
- The vote, the rating, and any structured reason categories the user selected
- The free-text comment the user typed
- The email address of the user who submitted the feedback
- Identifiers used to locate the request: trace ID, session identifiers, request token, and application or agent ID
- The page URL and the UI element the user gave feedback on
- Diagnostic labels attached to the request
- For search feedback, references to the results involved: the document ID, the datasource, the document type and category, and the position of the result
To remove the submitter's identity from the feedback record, contact Glean Support to request a deployment configuration change. This change does not remove the email address or user ID from the full Glean Customer Event feedback events written to your deployment.
Because a user can add sensitive content to a comment and the free-text comment is included in this payload, treat the comment field as the main privacy consideration. The payload omits the question and the response, but a comment that quotes them still conveys that content.
Consider a user who asks for an approved renewal budget, receives an incorrect figure, then downvotes with the comment "For the renewal, $5M is wrong. The signed agreement says $7M." The record Glean receives looks like this example payload:
{
"category": "CHAT",
"event": "MANUAL_FEEDBACK",
"manualFeedbackInfo": {
"source": "CHAT",
"vote": "DOWNVOTE",
"email": "user@example.com",
"traceId": "trace-123",
"comments": "For the renewal, $5M is wrong. The signed agreement says $7M."
}
}
The dedicated question and response fields are absent, but the copied comment still reveals the topic and both figures.
The absence of a field from the support feedback payload does not mean the field is never stored. Comments and conversation context are retained in your deployment, in the feedback store and in request logs. The copy of the Glean Customer Event feedback events in your deployment can also carry the comment and the user's question. The company email destination can carry the comment and the chat transcript. Those fields remain available to an authorized investigation.
Scrubbed feedback analytics
This record is written on every submission, regardless of the destination configuration. Most identifying fields are removed, pseudonymized, or hashed. It carries:
- The feedback category, the event type, and the vote
- The structured reason categories and the detail values the user selected
- A timestamp and the page path
- A pseudonymous user identifier, produced by salting and hashing the user ID. Not the email address
- The session tracking token, copied as-is and not hashed
- The application or agent ID
- The length and a salted hash of the structured feedback payload field. These describe the structured field, not the free-text comment
- For search, feed, and autocomplete feedback, the datasource, plus salted hashes of document IDs and URLs
This record does not carry the comment text, the submitter's email address, or the rating.
Feedback events in Glean Customer Event logs
Glean also writes feedback to the Glean Customer Event (GCE) logs as CHAT_FEEDBACK and SEARCH_FEEDBACK events. These events are separate from the support feedback payload. Glean writes them for eligible chat and search feedback, regardless of feedback-destination settings. Eligible chat feedback is an upvote, downvote, time-saved response, or submitted feedback form that Glean can tie to a single chat message, chat session, or agent run. Eligible search feedback is a submitted search feedback form. Feedback that a Glean engineer submits while acting as a user is not logged.
Each event is written twice:
- Copy in your deployment: written to the
glean-customer-eventlog in your own deployment project. By default, this copy is the full event. If raw logs are turned off for your deployment, this copy is the scrubbed event. To check which version your deployment writes, look at theIsScrubbedfield on an event in the log:falsemeans the full event. Glean does not receive this copy. - Scrubbed copy: written to the
scrubbed-glean-customer-eventlog, which Glean receives for analytics. This copy is always scrubbed.
The following table shows which fields each version of the event carries:
| Field | Full event | Scrubbed event |
|---|---|---|
| User ID | ✅ | Salted hash of the user ID |
| Submitter's email address and department name | ✅ | |
| Department ID | ✅ | ✅ |
| Vote, rating, and reason categories and their details | ✅ | ✅ |
| Time saved, for time-saved feedback | ✅ | ✅ |
| Free-text comment | ✅ | |
| The user's question for chat feedback, or the search query for search feedback | ✅ | |
| Chat identifiers: message ID, chat session ID, session tracking token, workflow ID, run ID, application ID, and agent ID | ✅ | ✅ |
| Search request tracking token, for search feedback | ✅ | ✅ |
| Trace ID, for chat feedback forms | ✅, when the trace is shared with the agent builder | ✅, when the trace is shared with the agent builder |
A trace is shared with the agent builder when a user submits feedback in their own chat with an agent, if your deployment supports sharing agent traces with builders. Sharing ends 30 days after the feedback is submitted.
GCE feedback events do not carry the response text, the chat transcript, citations, or document content.
In the full event, the free-text comment and the user's question stay in your deployment project. If you export GCE logs to another destination, such as BigQuery, the exported events carry the same fields. Apply the same access controls to the export that you apply to conversation content.
Downvote learning and evaluations
Glean uses downvotes to improve the product, but only within the personally identifiable information (PII) and defined permission controls. Downvotes supply Glean's customer health reporting, in aggregate form only. Glean uses this reporting for defect analysis, not product development.
Downvote learning and evaluations on downvoted queries run only on deployments that use the Glean Universal Model Key. How Glean processes a downvote depends on the LLM key your deployment uses:
| Key type | What happens when a user downvotes a chat |
|---|---|
| Customer Key | Glean receives a support ticket, and a Glean engineer diagnoses the issue manually. See Configure feedback destinations for which submissions file a ticket. No automated agent reads or parses the downvote data. Downvote learning and evaluations do not apply. |
| Glean Universal Model Key | An automated agent parses the downvote data to generate downvote learnings and to run evaluations on downvoted queries. See Glean Universal Model Key downvote learning. |
With either key type, Glean receives a support ticket only when the Glean destination is on. See Configure feedback destinations.
Glean Universal Model Key downvote learning
When a user downvotes an Assistant response in Thinking mode, the downvote can trigger an automated analysis of what went wrong. The analysis runs inside your deployment and produces a learning: a short record of the failure that tells Assistant what to do differently next time. When the same user later asks a similar question, Assistant retrieves the learning and uses it to avoid the same mistake.
Downvote learnings are scoped to the user who submitted the downvote:
- Each learning applies only to that user's future queries. It does not change responses for other users.
- Learnings are stored in your deployment.
When sharing with Glean is on, Glean receives the following analysis output:
- Classification labels
- The request identifiers
- Short summaries of the problem, written by a model
Glean does not receive the conversation, the documents, or the citations.
Glean also runs evaluations on downvoted queries. An automated judge measures how well responses align with the feedback the user gave. These evaluations follow the same permission guardrails as the rest of the Glean evaluation framework.
What Glean does not receive
The support feedback payload, the scrubbed feedback analytics, and the scrubbed copy of the GCE feedback events do not carry:
- The user's query text, the response text, or the chat transcript
- Previous messages in the conversation
- Citations and source references
- If a user reports a citation problem, Glean receives the reason category, such as an incorrect citation or a missing citation, without the citation itself.
- The reproduction URL, image URLs, and the raw structured feedback payload
- Reasoning traces, or details of tool and MCP execution
- The content of any document
Provide the minimum data for Glean support
To investigate a reported issue, Glean needs the trace ID and the session identifier to find the specific request. The trace ID and session identifier let Glean support locate the request without the conversation content. The rating and reason category tell support what went wrong.
If you disable sending feedback to Glean, supply the trace ID with your support ticket. Without it, support cannot reliably locate the request.
Understand how Glean engineers access conversation content
Access to conversation content is not a continuous data feed. A Glean engineer reaches it only through a high-sensitivity debug operation: a time-boxed access grant raised for a specific investigation.
Every high-sensitivity debug operation is recorded in the audit log, so you can review these operations yourself rather than requesting a record from Glean.
To download debug operation records from the audit log:
- In the Admin console, navigate to Users & permissions → Audit logs.
- Filter the logs by time range, or search by keyword to find the debug operations you want to review.
- Click Export to CSV.
The audit log keeps records for 30 days by default. To keep a longer record, export the logs regularly or contact your Glean representative to request a longer retention period. For Glean-hosted deployments, Glean can also set up ongoing delivery of audit logs to a destination you manage, such as your SIEM. Contact your Glean account team to set this up. See Audit logs.
Each request requires internal approval at Glean. For additional control, contact Glean Support to turn on the Customer Approval Flow. When the Customer Approval Flow is on, no Glean engineer reaches conversation content until one of your admins approves the request:
- Glean sends each request to your admins by email and in the Glean product.
- Your admins can grant or revoke access at any time.
- By default, each grant expires automatically after 7 days. To change this period, contact Glean Support.
Even with your approval, the Glean engineer still needs internal approval at Glean.
Act on feedback to improve response quality
Feedback is most useful when reviewed alongside broader troubleshooting, source quality, and agent performance data. A not-helpful rating often identifies:
- Ambiguous questions or missing context
- Poor source data
- Agent logic failures
To act on what feedback tells you:
- Refine prompts: Clear, specific questions lead to better answers. Consider user training on effective prompting.
- Improve data quality: Regularly update or deprecate inaccurate information in connected sources. Use the Verification feature of Glean where available.
- Optimize connectors: Organize documentation and clarify conflicting content to ensure the right information is accessible.
- Analyze patterns: Use feedback signals and comments to spot recurring issues. If systemic misfires persist, contact Glean Support for deeper tuning.
See also
- User feedback — how users submit feedback and what the feedback modal discloses