Pick a topic to dive in and start chatting with peers and Glean employees.
Posting a Feature Request on behalf of a customer, which resulted from a ticket: Quote below: When an admin connects a third-party MCP server (e.g., Wiz) to a Glean Agent via Actions, end users should not be required to individually authenticate against that MCP server. The admin who configures the Agent should be able to…
Description What we're requesting: A native Glean connector for Momentum — an AI Revenue Orchestration platform that captures structured data from customer interactions (Zoom calls, emails, Slack, CRM) and surfaces meeting transcripts, summaries, and AI-generated signals. Use case:We want to add Momentum content —…
Glean's key differentiator in the Enterprise is RBAC awareness. Identity Providers dictate and drive RBAC. For that reason Glean needs to be groups aware, not just user attribute aware. These are conceptual RBAC table stakes.
I'm trying to confirm if and how to get metadata columns in a sharepoint document library to be used by Glean when indexing. Here is an example use case - you have a Contracts Document Library and for this document library, you have extra metadata columns - like Region, Office, Industry that are not a part of the document…
Summary Request to enhance the Glean OAuth Authorization Server to support OAuth access token scoping at the data source level, and/or provide a mechanism to block issuance of tokens that have access to specific data sources. This capability is required for us to safely adopt Glean MCP server for our environment, where…
Summary We’re requesting the ability to limit OAuth clients and their tokens to specific Glean data sources through an explicit inclusion or exclusion mechanism. This configuration could be enforced at either the OAuth client level or via data-source-specific scopes—allowing administrators to define precisely which data…
Currently, when users initiate a chat via the Glean browser extension's pop-up dialog (such as by highlighting text and clicking the Glean icon), the chat session and its content are temporary. If the user clicks outside the pop-up or closes it, the chat and its responses are lost and do not appear in the main Glean Chat…
It would be great could include additional tables from Service-Now that are relevant to end users' requests and assigned assets: sc_req_item: Although Glean does crawl in the sc_request table, more relevant data to the request resides in the sc_req_item table since it contains more details about each individual requested…
Description Today, Glean’s Jira actions (used by Agents / Assistant) can only post public comments on Jira issues. Customers that use Jira heavily for support and operations often rely on internal-only comments for sensitive troubleshooting notes, handoffs, and internal coordination. Components Jira Actions - Create a Jira…
The default chat experience has followup question generation. it would be nice to add that to agents, especially if those follow-ups could be guided in some way.
Create an Idea post and tag it Feedback and Ideas so the community can upvote and our product team can prioritize it.
