Glean's search tool inherits whatever permissions were already wrong

The setup

Glean's task is narrower than a general chatbot: index a company's own documents, chats, and tickets, and answer a question by citing which internal source it drew from. Glean's enterprise search page states results are indexed in real time and that 'Glean enforces the existing permissions of your data sources in results, so users only see what they are allowed to access.' Connecting those sources is the actual setup work: Glean's connectors page states the product 'offers more than 250 connectors' into existing workplace systems. Neither page retrieved here links to a public price list; the site's calls to action are to request a demo, which is itself a setup cost worth naming before comparing this to a self-serve tool.

What the documents show

Glean's security page describes permission-checking as a design constraint rather than an optional filter, listing 'data permissions' as one of six 'AI security control points' and stating the system should 'enforce source-system permissions on every read and write' so 'an agent should not automatically access everything the user can.' The same page states every control point is logged to 'an end-to-end audit trail' that can stream into a security information and event management system. The enterprise-search page adds that when no document answers a query, Glean 'identifies subject-matter experts in your company' instead — the vendor's own description of the fallback behavior, not an independently verified outcome.

The friction

Respecting existing permissions is described as the core design goal, which means the tool's usefulness is bounded by how well those permissions were set in the source systems to begin with; the security page does not claim to fix mis-configured access controls in Slack, Google Drive, or a ticketing system, only to carry them forward. The absence of public pricing on both pages retrieved here means the actual cost of connecting 250-plus systems is not disclosed until a buyer talks to sales, which is a real setup cost for a team trying to compare tools before committing.

What changed in the work

Instead of asking a general assistant to guess at an answer, or asking a colleague to remember where they wrote something, a worker gets a cited pointer back to the internal document, chat, or ticket the answer came from, per the vendor's own description of the product. What that saves in practice — the actual minutes recovered from not searching four separate internal tools — is not measured on any page retrieved here; it is a plausible editorial read of the stated design, not a documented figure.

• Were the source system's permissions actually correct before this tool started surfacing what they allow?
• Does the tool say what happens when no internal document answers the question, or just imply it always finds one?
• What does connecting your specific mix of systems actually cost, and is that published anywhere?

A permissions-aware search layer is only as trustworthy as the access controls it inherits, and Glean's own materials describe carrying those controls forward rather than correcting them.