Glean Signals
What leaders and teams rolling out Glean report, with every finding tied to its evidence.
Read the findingsWhat the evidence says
Practitioner sentiment, all users
+67 Strong positive from 37 sources that take a side
How this figure is madeStrong positive overall signal, net 67 points
From 36 authors in 35 discussions. Run a pilot on questions your team already asks to measure how often the answer is right and cites its source.
- Analyzed
- 68 total sources
- Top praise
- Agents & Automation (15 of 19 sources) See praise evidence
- Top concern
- Setup & Administration (7 of 8 sources) See concern evidence
Jan 2025 to Sep 2026.
51 sources from practitioners, by month and sentiment.
The read is strongly positive. Cross-app search draws praise from 9 of 10 sources, and the 4 critical accounts on agents are GitHub reports of setup bugs in Glean's SDKs and MCP server. Assistant answers split, 4 positive to 4 critical, and 5 of the 6 sources on accuracy raise it. Saving time is the statement most sources share.
Positive, mixed and negative sources
The score counts them as 26 positive, 8 mixed and 2 negative votes, one per author. See How the numbers work.
See the evidenceBelow: 5 praise themes, 3 concerns and 2 close to agreement.
Findings
Counted for All users, from 51 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Agents & Automation15 of 19 sources on it praise itGlean Agents, Agent Builder, the APIs, and the MCP server used to automate work on company context.
Counted for All users.
Positive, 15
Positive
Madhu Narasimhan, CIO, DaVita Kidney Care
How DaVita Is Scaling AI in Healthcare With GleanPodcast show notes, The Ravit Show
DaVita's CIO discusses Glean's role as a context layer for scaling AI, stressing connected company knowledge and repeated correct answers as conditions for employee trust.
Positive
Hacker News commenter
Comment on: Ask HN: Who is using MCP in production?Hacker News comment
MCP remains the commenter's main way to use Cursor with enterprise systems such as Glean, Jira and Port.
Positive
Jay Rosenthal, Director of Business Intelligence, and Shashi Gupta, BI Platform Manager, at Motive
Bridging the Data Divide: How Motive Uses Glean and Snowflake Agents to Give Executives a 360° Account ViewEngineering blog post, Motive engineering blog
Motive's BI team uses a Glean agent as the orchestrator over Slack and Google Docs plus a Snowflake Cortex agent, and relies on Glean's source permissions while building its own for Snowflake.
Positive
reviewer2810748, Analyst at a financial services firm with 1, 001 to 5, 000 employees
Creating low-code agents has transformed policy queries and now saves employees hours dailyPeer review, PeerSpot
Built a branching agent that answers employee benefits and leave questions from long policy documents; enabling connectors took back-and-forth and custom actions lack request logs.
Positive
reviewer2809938, Senior Data Analyst at a tech vendor with 1, 001 to 5, 000 employees
Sales agents have automated prospect research and now save hours with unified customer insightsPeer review, PeerSpot
Built an agent for sales development reps that pulls from Gmail, Drive, Slack, Confluence, Salesforce and Gong; research that took hours now takes minutes, though it sometimes slows down.
Positive
Ananya Bl, Data Analyst at Capgemini
Daily orchestration of complex ai workflows has boosted my research and automation capabilitiesPeer review, PeerSpot
Got access through a Capgemini hackathon two months ago and now uses Glean daily, more than ChatGPT, to build and orchestrate agents.
Positive
Andy Chen (andychen32), Hacker News commenter and author of the post
Comment on: The Enterprise Context LayerHacker News comment
The author says the agents that built their company's context layer used Glean's search API, and that something like Glean is still needed for retrieval.
Positive
Ambsingh Singh, Senior Technical Program Manager at LinkedIn
AI assistants have transformed daily project decisions and documentation for complex programsPeer review, PeerSpot
Uses Glean daily for 20 months to review PRDs and draft plans with agents, saving one to two hours a week per program. This deployment does not crawl Teams and Outlook data.
Positive
Sravani Kakaraparthi, builds dbt models at their company
Automating dbt Documentation: A Workflow for Glean-Powered Column DescriptionsPersonal blog post, Medium
Built a Glean agent, called through the Python client, that finds business definitions for dbt columns; scoping it to knowledge sets cuts hallucinations, and a manual pass remains.
Positive
4mal6, Reddit commenter in r/ProductManagement
Comment on: Agents to help tackle all the little things in Jira and Figma?Reddit comment
During a trial the commenter built a Glean agent that proposed troubleshooting steps from documentation and past bugs, but the company chose ChatGPT instead.
Positive
Hacker News commenter
Comment on: What if you don't need MCP at all?Hacker News comment
Lists Glean among the MCP servers the commenter uses that work very well for teaching a model how to call a service's API.
Positive
Jackson Aaron, employee at a regulated firm
Glean: The Key to Enterprise AI Search and AgentsPersonal blog post, Medium
Two months in, Glean replaced seven tabs; results follow source permissions, and the author built an outreach agent but chose not to enable write actions.
Mixed
Zeeshan Safdar, subscription services representative at Pure Storage
Search for policies efficiently and build custom agents, but integration options still need improvementPeer review, PeerSpot
Uses Glean for a year to find policies and built a self-service agent, but Salesforce is not connected, and the reviewer believes no teammate uses it regularly.
Positive
Gopi Gonuguntla, Principal Architect at a tech vendor with 10, 001+ employees
AI agents have transformed how we compare offers and standardize complex project documentsPeer review, PeerSpot
Almost two years in, the reviewer's teams save one to 1.5 hours a day; the reviewer values permission awareness and a choice of 15+ models, and evaluated Microsoft Copilot first.
Positive
Andy Chen, built a question bot for go-to-market reps at Abnormal
The Enterprise Context LayerPersonal blog post, andychen32.substack.com
Abnormal recently adopted Glean, which the author calls excellent at finding documents and used heavily while onboarding; it does not synthesize the judgment calls a question bot needed.
Mixed or negative, 4
No opinion stated
sammcj, developer filing a GitHub issue
The many agent skills under skills/ should really just be a single skillGitHub issue
The Glean CLI ships many small agent skills whose descriptions all load into every coding-agent session, so the author merged them into one skill of his own.
No opinion stated
yurykar, developer filing a GitHub issue
upload_files()/upload_files_async() raises httpx.RequestNotReadGitHub issue
Glean's official file-upload example for agents failed on every call, because a request hook read the multipart body before it was sent.
No opinion stated
ryan-macdonald-nb, developer filing a GitHub issue
Global token auth sends wrong header: X-Glean-Act-As instead of X-Glean-ActAsGitHub issue
With a global token, the Glean MCP server sent a misspelled act-as header, so every tool call failed with a 400 until the header name was corrected.
No opinion stated
gamisn, developer filing a GitHub issue
GleanSearchRetriever fails silently on authentication errorsGitHub issue
Glean's LangChain retriever returned an empty list on a bad token or instance without raising an error. Misconfiguration looked the same as no results.
Cross-App Search9 of 10 sources on it praise itFinding the right document, thread, or answer across several work apps from one search, faster than each app's own search.
Counted for All users.
Positive, 9
Positive
reviewer2809308, Senior Support Engineer at a software company with 501 to 1, 000 employees
Unified data search has improved cross-team insights and speeds up resolving recurring issuesPeer review, PeerSpot
Searching Confluence and Jira together beats each tool's own search; licenses were expensive and hard to justify, so the reviewer advises trialing adoption with several groups first.
Positive
Hacker News commenter
Comment on: How do you capture WHY engineering decisions were made, not just what?Hacker News comment
Decisions that moved into Jira and Confluence became hard to find; AI search tools such as Glean and Rovo have improved discoverability.
Positive
Andy Chen, built a question bot for go-to-market reps at Abnormal
The Enterprise Context LayerPersonal blog post, andychen32.substack.com
Abnormal recently adopted Glean, which the author calls excellent at finding documents and used heavily while onboarding; it does not synthesize the judgment calls a question bot needed.
Positive
Tarun Garg, Resident Solution Architect at Starburst
Great product to useTrustRadius review
Starburst connected Glean to Slack, Confluence, and email; the reviewer uses search and chat across them daily and wants file and image upload next.
Positive
Account Manager in Customer Service at a security and investigations company
Easy as 12 GleanTrustRadius review
An account manager finds product docs and last year's approved payment terms in Glean during customer calls, though results sometimes rank older material above current.
Positive
Hacker News commenter
Comment on: How the AI Bubble Will PopHacker News comment
Skeptical of the wider AI buildout, the commenter still values internal search and chat and says Glean at work is great.
Positive
Hacker News commenter
Comment on: Why is AI so slow to spread?Hacker News comment
The commenter's employer has Glean search, which beats Atlassian's for Jira and Confluence and also searches Slack and Google Drive.
Positive
Hacker News commenter
Comment on: Ask HN: Is every company's internal wiki just broken by default?Hacker News comment
The commenter's answer to broken internal wikis is to use Glean, a smart search across Confluence, Slack, Google Docs and Outlook.
Positive
Kavita Khandhadia, Senior Partner, Global Alliances, at a software company with 1, 001 to 5, 000 employees
Centralized search has transformed my research workflow and saves hours on complex data gatheringPeer review, PeerSpot
In a one-month trial, a day's research took two hours; it also returned the wrong image and a confusing Confluence link, and the reviewer recommends it where budget allows.
Mixed or negative, 1
Mixed
Hacker News commenter
Comment on: The Enterprise Context LayerHacker News comment
The commenter found Cursor with Claude over Slack and Google Workspace MCP connections answered questions well and much faster than Glean.
Connector Coverage7 of 10 sources on it praise itHow many of the author's work apps Glean connects to and indexes, and how well.
Counted for All users.
Positive, 7
Positive
reviewer2809692, Librarian at a university with 1, 001 to 5, 000 employees
Intuitive workflows have improved integrations and streamlined daily management tasksPeer review, PeerSpot
After 18 months, integrations work with all of the university's other platforms; licensing options are limited.
Positive
Jackson Aaron, employee at a regulated firm
Glean: The Key to Enterprise AI Search and AgentsPersonal blog post, Medium
Two months in, Glean replaced seven tabs; results follow source permissions, and the author built an outreach agent but chose not to enable write actions.
Positive
Jay Rosenthal, Director of Business Intelligence, and Shashi Gupta, BI Platform Manager, at Motive
Bridging the Data Divide: How Motive Uses Glean and Snowflake Agents to Give Executives a 360° Account ViewEngineering blog post, Motive engineering blog
Motive's BI team uses a Glean agent as the orchestrator over Slack and Google Docs plus a Snowflake Cortex agent, and relies on Glean's source permissions while building its own for Snowflake.
Positive
reviewer2809938, Senior Data Analyst at a tech vendor with 1, 001 to 5, 000 employees
Sales agents have automated prospect research and now save hours with unified customer insightsPeer review, PeerSpot
Built an agent for sales development reps that pulls from Gmail, Drive, Slack, Confluence, Salesforce and Gong; research that took hours now takes minutes, though it sometimes slows down.
Positive
Tarun Garg, Resident Solution Architect at Starburst
Great product to useTrustRadius review
Starburst connected Glean to Slack, Confluence, and email; the reviewer uses search and chat across them daily and wants file and image upload next.
Positive
Hacker News commenter
Comment on: Ask HN: Is every company's internal wiki just broken by default?Hacker News comment
The commenter's answer to broken internal wikis is to use Glean, a smart search across Confluence, Slack, Google Docs and Outlook.
Positive
Hacker News commenter
Comment on: Indexing Code at Scale with GleanHacker News comment
Glean's answers cite the commenter's internal Jira, wiki, Slack and GitHub, and it summarizes a busy Slack channel's past week.
Mixed or negative, 3
Mixed
Zeeshan Safdar, subscription services representative at Pure Storage
Search for policies efficiently and build custom agents, but integration options still need improvementPeer review, PeerSpot
Uses Glean for a year to find policies and built a self-service agent, but Salesforce is not connected, and the reviewer believes no teammate uses it regularly.
Positive
Ambsingh Singh, Senior Technical Program Manager at LinkedIn
AI assistants have transformed daily project decisions and documentation for complex programsPeer review, PeerSpot
Uses Glean daily for 20 months to review PRDs and draft plans with agents, saving one to two hours a week per program. This deployment does not crawl Teams and Outlook data.
Mixed
Savannah Hair, Account Executive at Carta
Glean Vs. GuruTrustRadius review
A Carta account executive says Glean chat gives wrong answers about the sales process and some documents from Guru went missing after the move; the reviewer would not buy it again.
Permission-Aware Results5 of 6 sources on it praise itResults and answers that follow the permissions set in each source app.
Counted for All users.
Positive, 5
Positive
Jackson Aaron, employee at a regulated firm
Glean: The Key to Enterprise AI Search and AgentsPersonal blog post, Medium
Two months in, Glean replaced seven tabs; results follow source permissions, and the author built an outreach agent but chose not to enable write actions.
Positive
Jay Rosenthal, Director of Business Intelligence, and Shashi Gupta, BI Platform Manager, at Motive
Bridging the Data Divide: How Motive Uses Glean and Snowflake Agents to Give Executives a 360° Account ViewEngineering blog post, Motive engineering blog
Motive's BI team uses a Glean agent as the orchestrator over Slack and Google Docs plus a Snowflake Cortex agent, and relies on Glean's source permissions while building its own for Snowflake.
Positive
Gopi Gonuguntla, Principal Architect at a tech vendor with 10, 001+ employees
AI agents have transformed how we compare offers and standardize complex project documentsPeer review, PeerSpot
Almost two years in, the reviewer's teams save one to 1.5 hours a day; the reviewer values permission awareness and a choice of 15+ models, and evaluated Microsoft Copilot first.
Positive
Beef410, Reddit commenter in r/sysadmin
Comment on: Why aren't more companies feeding their internal docs/code into an internal RAG system?Reddit comment
The commenter's company uses Glean over SharePoint and other data, and each user's results include only what that person has permission to see.
Positive
reviewer2809938, Senior Data Analyst at a tech vendor with 1, 001 to 5, 000 employees
Sales agents have automated prospect research and now save hours with unified customer insightsPeer review, PeerSpot
Built an agent for sales development reps that pulls from Gmail, Drive, Slack, Confluence, Salesforce and Gong; research that took hours now takes minutes, though it sometimes slows down.
Mixed or negative, 1
No opinion stated
VirajParmar06, developer filing a GitHub issue
assert_negative_identities_absent does not inspect allowAnonymousAccess or allowAllDatasourceUsersAccessGitHub issue
The indexing SDK's permission check passes documents opened to anonymous or all-datasource access. In the reporter's connector, 41.3% of 28,449 messages had no clear owner, the case where such broad access gets set.
Grounded Answers4 of 8 sources on it praise itGlean Assistant answers and summaries built from company sources, with citations.
Counted for All users.
Positive, 4
Positive
Madhu Narasimhan, CIO, DaVita Kidney Care
How DaVita Is Scaling AI in Healthcare With GleanPodcast show notes, The Ravit Show
DaVita's CIO discusses Glean's role as a context layer for scaling AI, stressing connected company knowledge and repeated correct answers as conditions for employee trust.
Positive
reviewer2783439, DevOps and sales operations at a marketing services firm with 51 to 200 employees
Consolidating marketing content has streamlined sales prospect outreach and collaborationPeer review, PeerSpot
Set Glean up for the sales team to pull together prospect material through the chatbot; rates it nine of ten, though the integrations were hard to understand.
Positive
Kelly Guslani, Recruiter at Databricks
You must get Glean if you care about your employeesTrustRadius review
A Databricks recruiter uses Glean chat during interviews to answer candidates' questions about teams and offices, with the sources shown; the reviewer finds the thinking step slow.
Positive
Hacker News commenter
Comment on: Indexing Code at Scale with GleanHacker News comment
Glean's answers cite the commenter's internal Jira, wiki, Slack and GitHub, and it summarizes a busy Slack channel's past week.
Mixed or negative, 4
Positive
Andy Chen, built a question bot for go-to-market reps at Abnormal
The Enterprise Context LayerPersonal blog post, andychen32.substack.com
Abnormal recently adopted Glean, which the author calls excellent at finding documents and used heavily while onboarding; it does not synthesize the judgment calls a question bot needed.
Negative
Tagir Valeev, software engineer
Glean in Slack answers a real fire alarmMastodon post
When a colleague asked in Slack about a fire alarm, Glean privately told them it was a scheduled test and they could stay at their desk. It was a real alarm.
Mixed
Savannah Hair, Account Executive at Carta
Glean Vs. GuruTrustRadius review
A Carta account executive says Glean chat gives wrong answers about the sales process and some documents from Guru went missing after the move; the reviewer would not buy it again.
Negative
Hacker News commenter
Comment on: My AI skeptic friends are all nutsHacker News comment
Docs colleagues produce by asking Glean are misleading to badly wrong four times in five on topics the commenter knows; internal terminology derails it.
What concerns them
Every concern practitioners raise, most raised first.
Setup & Administration7 of 8 sources on it raise it as a concernConnector setup, integrations, agent configuration, and the admin work a deployment takes.
Counted for All users.
Raised as a concern, 7
No opinion stated
ryan-macdonald-nb, developer filing a GitHub issue
Global token auth sends wrong header: X-Glean-Act-As instead of X-Glean-ActAsGitHub issue
With a global token, the Glean MCP server sent a misspelled act-as header, so every tool call failed with a 400 until the header name was corrected.
No opinion stated
gamisn, developer filing a GitHub issue
GleanSearchRetriever fails silently on authentication errorsGitHub issue
Glean's LangChain retriever returned an empty list on a bad token or instance without raising an error. Misconfiguration looked the same as no results.
Mixed
Steve Januario, CIO, Bill.com
From Risk to Resilience: What Bill.com's CIO Learned Deploying Copilot, Gemini, and GleanWebcast recap, Opsin blog
Bill.com's CIO reports that deploying AI search tools such as Glean surfaced misconfigured permissions, open Jira boards, and onboarding files with sensitive data. He rolled them out through phased pilots with legal and security.
No opinion stated
sammcj, developer filing a GitHub issue
The many agent skills under skills/ should really just be a single skillGitHub issue
The Glean CLI ships many small agent skills whose descriptions all load into every coding-agent session, so the author merged them into one skill of his own.
No opinion stated
yurykar, developer filing a GitHub issue
upload_files()/upload_files_async() raises httpx.RequestNotReadGitHub issue
Glean's official file-upload example for agents failed on every call, because a request hook read the multipart body before it was sent.
Positive
reviewer2810748, Analyst at a financial services firm with 1, 001 to 5, 000 employees
Creating low-code agents has transformed policy queries and now saves employees hours dailyPeer review, PeerSpot
Built a branching agent that answers employee benefits and leave questions from long policy documents; enabling connectors took back-and-forth and custom actions lack request logs.
Positive
reviewer2783439, DevOps and sales operations at a marketing services firm with 51 to 200 employees
Consolidating marketing content has streamlined sales prospect outreach and collaborationPeer review, PeerSpot
Set Glean up for the sales team to pull together prospect material through the chatbot; rates it nine of ten, though the integrations were hard to understand.
Discussed without concern, 1
Positive
Jay Rosenthal, Director of Business Intelligence, and Shashi Gupta, BI Platform Manager, at Motive
Bridging the Data Divide: How Motive Uses Glean and Snowflake Agents to Give Executives a 360° Account ViewEngineering blog post, Motive engineering blog
Motive's BI team uses a Glean agent as the orchestrator over Slack and Google Docs plus a Snowflake Cortex agent, and relies on Glean's source permissions while building its own for Snowflake.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Initial crawl time depends on content volume and source API limits. The Admin console shows crawl status and rate for each connector. Crawling FAQ
Open them in the recordAnswer Accuracy5 of 6 sources on it raise it as a concernWrong or incomplete answers, including misleading output and answers based on stale or casual content.
Counted for All users.
Raised as a concern, 5
Positive
Kavita Khandhadia, Senior Partner, Global Alliances, at a software company with 1, 001 to 5, 000 employees
Centralized search has transformed my research workflow and saves hours on complex data gatheringPeer review, PeerSpot
In a one-month trial, a day's research took two hours; it also returned the wrong image and a confusing Confluence link, and the reviewer recommends it where budget allows.
Negative
Tagir Valeev, software engineer
Glean in Slack answers a real fire alarmMastodon post
When a colleague asked in Slack about a fire alarm, Glean privately told them it was a scheduled test and they could stay at their desk. It was a real alarm.
Mixed
Savannah Hair, Account Executive at Carta
Glean Vs. GuruTrustRadius review
A Carta account executive says Glean chat gives wrong answers about the sales process and some documents from Guru went missing after the move; the reviewer would not buy it again.
Negative
Hacker News commenter
Comment on: My AI skeptic friends are all nutsHacker News comment
Docs colleagues produce by asking Glean are misleading to badly wrong four times in five on topics the commenter knows; internal terminology derails it.
Positive
Account Manager in Customer Service at a security and investigations company
Easy as 12 GleanTrustRadius review
An account manager finds product docs and last year's approved payment terms in Glean during customer calls, though results sometimes rank older material above current.
Discussed without concern, 1
Positive
Sravani Kakaraparthi, builds dbt models at their company
Automating dbt Documentation: A Workflow for Glean-Powered Column DescriptionsPersonal blog post, Medium
Built a Glean agent, called through the Python client, that finds business definitions for dbt columns; scoping it to knowledge sets cuts hallucinations, and a manual pass remains.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Teams can publish authoritative Answers, mark documents verified or out of date, and pin results. Admins set inclusion and exclusion rules for each connector. Populate content
Open them in the recordPrice & Licensing3 of 6 sources on it raise it as a concernSeat cost, contract size, pricing that is not published, and licensing options.
Counted for All users.
Raised as a concern, 3
Mixed
Hacker News commenter
Comment on: Software engineering is about managing complexityHacker News comment
Sharing context is the hard limit for AI at work; unifying search tools like Glean help a lot but are expensive.
Positive
reviewer2809308, Senior Support Engineer at a software company with 501 to 1, 000 employees
Unified data search has improved cross-team insights and speeds up resolving recurring issuesPeer review, PeerSpot
Searching Confluence and Jira together beats each tool's own search; licenses were expensive and hard to justify, so the reviewer advises trialing adoption with several groups first.
Mixed
Hacker News commenter
Comment on: Indexing Code at Scale with GleanHacker News comment
After an intro meeting, the commenter judged Glean's pricing to make sense only at 100 to 150+ employees, recalling a US$50k yearly starting point with a caveat.
Discussed without concern, 3
Positive
reviewer2809692, Librarian at a university with 1, 001 to 5, 000 employees
Intuitive workflows have improved integrations and streamlined daily management tasksPeer review, PeerSpot
After 18 months, integrations work with all of the university's other platforms; licensing options are limited.
Positive
Kavita Khandhadia, Senior Partner, Global Alliances, at a software company with 1, 001 to 5, 000 employees
Centralized search has transformed my research workflow and saves hours on complex data gatheringPeer review, PeerSpot
In a one-month trial, a day's research took two hours; it also returned the wrong image and a confusing Confluence link, and the reviewer recommends it where budget allows.
Positive
Gopi Gonuguntla, Principal Architect at a tech vendor with 10, 001+ employees
AI agents have transformed how we compare offers and standardize complex project documentsPeer review, PeerSpot
Almost two years in, the reviewer's teams save one to 1.5 hours a day; the reviewer values permission awareness and a choice of 15+ models, and evaluated Microsoft Copilot first.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Glean publishes its pricing structure but no list price. Seats are licensed per user per month. Premium models, agent runs, and other advanced features draw on pooled FlexCredits or Model Hub usage under the contract. Glean Enterprise Flex pricing
Open them in the record
Where the evidence agrees
Statements this group's sources agree on, then the ones close to agreement.
Close to agreement: each needs 11 supporting sources
- Below threshold
Glean saves time when people find information across tools or answer questions that would otherwise reach colleagues.
8 supporting sources - Below threshold
Glean replaces each work app's own search with a single search across all of them.
6 supporting sources
Where it disagrees
Questions the sources split on, with the count on each side.
For all users, no question reaches 5 sources from 3 authors, with 2 on each side.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All users. Leaders and teams have 14 accounts; GILD prints their sentiment from 20.
Leaders and teams rolling it out
22 sources. These accounts focus on agents, permissions, setup work, adoption, and cost, from the accounts of teams and companies that rolled Glean out or built on it.
Individual users
29 sources. These accounts focus on day-to-day search, answers, and connectors for one person using Glean at work.
All users
51 sources. This gives the broadest read. It mixes individual users with company-wide rollouts, and the two can reach different conclusions.
51 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual userOne person using it for their own work29 sources, counted here
Emphasizes Cross-app search, connectors, and answer accuracy
- Small team2 to 10 people sharing it2 sources, counted here
Emphasizes Price at small company sizes, and building an alternative
- DepartmentA department, or a named company's team13 sources, counted here
Emphasizes Agents built for a department, permissions, and setup work
- IT & leadershipIT and business leaders deciding the rollout6 sources, counted here
Emphasizes A CIO on the oversharing that AI search surfaced, and phased pilots run with legal and security
- Organization-wideCompany-wide rollout1 sources, counted here
Emphasizes McCarthy's AI program lead describes a company-wide rollout; measure retained active use after 90 days
What changes with scale. Individual users talk most about finding things across apps and about answers that go wrong. Team and company accounts shift toward agents, permissions, setup work, and whether usage justifies the contract.
Where the sources come from
Where this group's sources were published.
Counted for All users, from 51 sources. Change group
68 sources for this group, 17 of them documentation
- Business Blogs & Reviews26, 38% of 68 sources
- Online Communities & Issue Trackers24, 35% of 68 sources
- Product Documentation17, 25% of 68 sources
- Podcasts, Talks & Videos1, 1% of 68 sources
Older evidence is retained when it still applies. Sources about earlier pricing or Assistant answers on earlier models stay in the history, marked Needs a recheck.
See sources by originThe record
Who each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 68 sourcesAbout this read
What changed, and how we count
What changed
- Nov 1, 2026: since Oct 30 the page prints one vote per author, and a figure given on the weighted reading is the second view. Individual users read +74 and all users +67; leaders and teams are unscored.
- Oct 30, 2026: a second-model check removed an X post that names no organization, use or outcome, leaving 51 public accounts, the newest from Sep 22, 2026. Bill.com's card no longer says the company fixed the files as search went live, and its Copilot comparison account leaves, since Opsin, which published the recap, sells data-security tools for these rollouts. Expedia's card now says Expedia pitched summarization to the team that built a queryable replacement for its QBR.
- Builds the evidence base from public sources only: every source links to the page it comes from and names its author and publication date.
- Shows a finding in a view only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
- Adds Permission-Aware Results as a praise theme, since sources praise how results follow source permissions. On October 25, 2026 GILD searched security research and the press and found no report of Glean showing anyone content their source permissions hid. The one stored permission report is a GitHub issue: the indexing SDK's permission check passes documents open to all datasource users. In the reporter's connector 41.3% of 28,449 messages had no clear owner. Before rollout, audit broadly shared folders and channels, and check sensitive documents with Glean's access verification in the Admin console.
- Drops Onboarding & Discovery (4 sources) and the buy-versus-build, standalone-versus-suite, and worth-the-price disagreements, none of which reach 2 sources on each side.
- Excludes Glean employees, partners, and resellers writing about the product, and checks every documentation page against Glean's current docs.
- Removes 10 sources that missed the source standard, 7 of them published before 2025. Adds 9 from TrustRadius, Reddit, Hacker News, and Mastodon. The statement on content quality loses its last source and is dropped.
- Oct 25, 2026: adds 6 GitHub issues from developers building on Glean's MCP server, API clients, CLI, and indexing SDK. Setup & Administration now reaches 5 sources from 3 authors, and Agents & Automation records its first critical accounts.
- Oct 26, 2026: adds four further customer session accounts from Etsy, Pure Storage, McCarthy, and Howard Hughes, with first-party speaker roles and exact quote evidence.
- Oct 26, 2026: adds named rollout accounts from Bill.com, McCarthy, HubSpot, and DaVita, with exact quotes. They cover permissions, adoption, and connected company context.
- Lists six talks from webinars and conferences Glean ran without counting them. On the weighted reading, leaders and teams fall from 20 sources to 14, under the 20 a score needs, so the practitioner sentiment the page then printed moves from +76 for leaders and teams to +66 for all practitioners.
- Oct 28, 2026: adds 2 sources from GILD's research ledger with the passages they quote: Brex's CTO on teams building Glean agents, on Latent Space, and an X post from a Glean user. Neither states an overall opinion, so the scores do not move. Thirteen more research records came from Glean's own community forum and stay out, since a vendor's own site cannot carry practitioner evidence.
Method
A running review of what people using Glean at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
- Leaders and teams rolling it out
- Small team, Department, IT & leadership, Organization-wide
- Individual users
- Individual user
- All users
- Everyone in the leaders and teams and individual users groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
- Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among IT and business leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
- Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all users read +66 strong positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
- Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +66 Strong positive; with one vote per author it reads +67 Strong positive. No evidence changed.
- Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
- Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
- Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
- Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
- Disagreements. The count on each side. GILD names no winner and gives no share of all users.
- Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
- Documented
- Stated in official documentation.
- Reported
- A practitioner's account of their own use.
- Measured
- Backed by the source's own measurements, such as a comparative test or tracked team metrics.
- GILD analysis
- GILD's check of a claim against official documentation.
- Current
- Describes the product as it is now.
- Still applicable
- Older, and the behavior or lesson still holds.
- Needs a recheck
- May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
- Out of date
- No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 1 of 14, individual users 0 of 23, all users 1 of 37.
Limits
- These figures cover 51 reviewed public sources; they do not represent all customers. Hacker News supplies 14, PeerSpot 10, GitHub issues 6, TrustRadius 4, Reddit 3, and customer sessions, named blogs and posts the rest. The GitHub issues come from developers building on Glean's APIs, SDKs, and MCP server, so the GitHub reports lean toward setup bugs. Of the 10 PeerSpot reviews, 9 appeared between March 14 and 23, 2026, in what reads as one review collection drive. Six customer talks come from webinars and conferences Glean ran; they are listed and not counted. G2, Capterra, and Gartner Peer Insights block automated reading. GILD checked the Latent Space, Practical AI, and Software Engineering Daily podcast feeds, where Glean comes up only with investors and former Glean staff, whom the source standard excludes.
- Sources rarely name the Glean plan or the model behind an answer; each source shows what it states. Accounts of pricing, or of Assistant answers before 2025, are marked Needs a recheck.
Every count, and the sources behind it
14 findings for 3 groups
Each row opens its sources for the group you are reading.
| Finding | Leaders and teams rolling it out | Individual users | All users | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 9 positive, 4 mixed, 1 negative | 18 positive, 4 mixed, 1 negative | 27 positive, 8 mixed, 2 negative | Sources |
| PraiseCross-App Search | 1 of 1 positive (under the minimum) | 8 of 9 positive | 9 of 10 positive | Sources |
| PraiseConnector Coverage | 2 of 2 positive (under the minimum) | 5 of 8 positive | 7 of 10 positive | Sources |
| PraiseGrounded Answers | 2 of 4 positive (under the minimum) | 2 of 4 positive (under the minimum) | 4 of 8 positive | Sources |
| PraiseAgents & Automation | 8 of 8 positive | 7 of 11 positive | 15 of 19 positive | Sources |
| PraisePermission-Aware Results | 3 of 3 positive (under the minimum) | 2 of 3 positive (under the minimum) | 5 of 6 positive | Sources |
| ConcernPrice & Licensing | 1 of 2 raise it (under the minimum) | 2 of 4 raise it (under the minimum) | 3 of 6 raise it | Sources |
| ConcernAnswer Accuracy | 1 of 1 raise it (under the minimum) | 4 of 5 raise it | 5 of 6 raise it | Sources |
| ConcernSetup & Administration | 3 of 4 raise it (under the minimum) | 4 of 4 raise it (under the minimum) | 7 of 8 raise it | Sources |
| ConcernAdoption | 2 of 2 raise it (under the minimum) | 1 of 2 raise it (under the minimum) | 3 of 4 raise it (under the minimum) | Sources |
| ConsensusSaves time finding information | 3 supporting (under the minimum) | 5 supporting (below threshold) | 8 supporting (below threshold) | Sources |
| ConsensusOne place to search | 0 supporting (under the minimum) | 6 supporting | 6 supporting (below threshold) | Sources |
| ConsensusSuite assistants overlap | 2 supporting (under the minimum) | 0 supporting (under the minimum) | 2 supporting (under the minimum) | Sources |
| Current readEvidence mix | 39 sources | 46 sources | 68 sources | Sources |
Fact checks
GILD's checks of claims against official documentation, kept apart from the source counts.
- Price & Licensing. Glean publishes its pricing structure but no list price. Seats are licensed per user per month. Premium models, agent runs, and other advanced features draw on pooled FlexCredits or Model Hub usage under the contract. Glean Enterprise Flex pricing, checked Oct 12, 2026
- Answer Accuracy. Teams can publish authoritative Answers, mark documents verified or out of date, and pin results. Admins set inclusion and exclusion rules for each connector. Populate content, checked Oct 12, 2026
- Setup & Administration. Initial crawl time depends on content volume and source API limits. The Admin console shows crawl status and rate for each connector. Crawling FAQ, checked Oct 12, 2026
- Adoption. Glean recommends a staggered rollout that starts with about 100 to 300 users from several departments, with surveys, training, and office hours before a wider launch. Rollout strategy, checked Oct 12, 2026