Identity
- SSO
- People Data
- Roles
Assistant
- Configuration
- Features
- Apps
- Actions
- Data Analysis
- Slackbot
- Glean Assist
Knowledge
- Announcements
- Answers
- People & Teams
Management
- Alerts
- Glean Apps
- Customization
Insights
Developer
FAQ
Frequently asked questions about Glean Apps, including setup, deployment, functionality, and troubleshooting
General Information
Glean Apps are self-serve, no-code solutions that allow users to build and deploy customized AI Assistants in minutes. These apps can perform defined functions within an organization, such as answering frequently asked questions in a specific Slack channel. They pull information from a precise set of data sources and follow existing user permission and data governance rules.
Glean workspace admins and super admins can create, view, edit, and delete any Glean App. They can also grant ‘Glean App Creator’ permissions to other members, allowing them to create, edit, and delete their own Glean Apps.
Each App can have multiple editors who help manage it. More information is available in this help article.
Admins can grant Glean App Creator permission in two ways:
- Member-by-member basis from the workspace settings
- Provide app creator permission as a default for app members
More information is available in this help article.
Deployment and Access
Currently, Glean Apps can be deployed to:
- Chat
- Slack channels
- Chat API
- Web embeds
Yes, you can choose if a Glean App is visible to either all or some of your teammates. Teammates can always access the App using the test link.
Functionality and Use Cases
Glean Apps can be used in various scenarios:
Employee Experience
- IT help desk agents
- HR queries
- Company-wide employee experience bots
- Personalized onboarding
- Internal communications
Sales and Marketing
- Answering customer questions
- Crafting personalized emails
- Summarizing meeting notes
- Competitive intelligence
Product and Engineering
- Synthesizing customer feedback
- Answering questions in Slack/Teams
- Generating project updates
- Managing technical documentation
Customer Support
- Suggesting case resolutions
- Creating service briefings
- Managing knowledge base articles
Glean Apps use retrieval-augmented generation (RAG) to ensure answers are grounded in the specified knowledge sources. They provide line-by-line citations for the content used to generate responses. Response instructions can also be used to direct the App to keep answers concise and optimize for brevity.
Glean Apps differ from Glean Assistant in two key ways:
- They only refer to the knowledge sources that these Apps have access to answer the questions
- App creators can provide additional instructions to customize the behavior and personality of the Glean App
Currently Assistant and Glean Apps use the same LLM that is set up for your workspace. The ability to choose a different LLM provider and key for different Glean Apps is not available.
Publishing Glean Apps to Slack
Publishing a Glean App to a test channel is the recommended approach for testing. This allows you to verify the app’s functionality and accuracy before deploying it to a broader audience.
If you assign a Glean app to a channel that already has Gleanbot, the app will replace Gleanbot.
If a channel already has a Glean app, you can’t add another app to that channel. In the app builder, we display a warning icon in the dropdown list of channels if a Slack channel already has an app.
Troubleshooting and Best Practices
If a Glean App is not providing accurate responses, it may be due to one of the following reasons:
- Misconfigured instructions
- Limitations with media data
- Known limitations with Glean’s existing connectors
- Insufficient or overly similar data sources
Content which is already crawled and indexed by Glean’s connectors is instantly usable when added as a knowledge source in a Glean app. Updates for newly created or recently updated content and changes in recursive folder structure follow the SLA for their respective Glean connector.
Was this page helpful?