Pick a topic to dive in and start chatting with peers and Glean employees.
Hello, Glean is not accessible to everyone in my organization. If I configure the Service Cloud embedded integration, will the glean interface elements still show up for every end user in service cloud, or only those users who have access to glean?
I'm wondering if we should target specific groups or make more general shares. Also, is there a way to promote good prompts inside Glean itself: "Hey everyone, try this one!"?
Idea Match how many customers actually structure their companies. A common pattern is: Company Org / Business Unit (e.g., Technology, Customer Operations) Department / Team within that org (e.g., Support, Knowledge Management) Right now there’s no first-class Org layer in Glean for either: The People Profile (what shows…
Join us on 10/17 at 10am PT for a hands-on AIOM Office Hours session with @Yan Katcharovski & @goose. During this session Yan & Gustav will build a working agent to lessen the friction of tedious CRM updates. ➡️ Gleaniverse sign up link What you’ll see: A live build of an agent that auto-updates Salesforce Opportunities…
Restaurant365 is looking for a Senior Integrations Engineer to own and evolve our Glean integrations ecosystem - with a strong emphasis on APIs, custom data sources, and custom actions/tooling that make enterprise knowledge reliably discoverable across our SaaS stack. If you’re active in Glean (especially building custom…
We request native connectors for Microsoft Planner and Microsoft To Do. We currently use Microsoft Planner and Microsoft To Do. Access to this information would facilitate its utilization. We expect the implementation of native connectors, not custom connectors.
FEATURE REQ: Glean insights dashboards display data in real time, eliminate 1 day lag. WHY: Enable ability to see real time/to current time usage for current day. 1 day lag limits usefulness of insights capability.
When building more complex, longer-running agents, one of the main things that slows down development is needing to fully replay the workflow to test after modifying one node. It would be cool if there were a way to test specific nodes either with mock input data or by using the inputs from the previous run.
I'm using Glean as one of my tools to do deep research on a domain that is new to me. I work within a large complex org, and Glean is ingesting a lot of content across it Part of my learning is trying to learn more from outside my work and immediate domain. However, what I'm observing is that the prioritization of sources…
Description: For Confluence, customers need Glean to show the current space name/alias rather than the old immutable key. Example: A client renamed their space from “ALPHA” to “BETA.” Confluence shows “BETA” and redirects correctly, but the API still returns the ALPHA key/URL, so Glean surfaces the old name. While this…
Create an Idea post and tag it Feedback and Ideas so the community can upvote and our product team can prioritize it.