Knowledge profiles
Knowledge profiles let admins define the company knowledge that Gleanbot and public data agents can search. A profile sets a bounded corpus of connectors and, where supported, specific workspaces, repositories, groups, or teams.
Company knowledge profile
Every deployment includes a default Company knowledge profile. If Gleanbot already has public data settings, Glean carries those settings into the profile. Otherwise, Glean initializes the profile with its recommended Tier 1 connectors.
The Company knowledge profile is the default corpus for public Gleanbot responses and for auto-agents configured to use public data. Review the profile before you share an agent in a Slack channel, collaborative workflow, or another surface where multiple people can see its responses.
Configure a knowledge profile
- In the Admin console, go to Agents → Knowledge Profiles.
- Open the profile you want to configure.
- Add or remove connectors from the profile.
- Configure source specific scope for connectors that support it.
- Save your changes.
Supported controls
You can include or exclude any supported connector within a profile. The connectors below allow for even more granular scoping:
| Connector | Scope you can select |
|---|---|
| Slack and Slack Enterprise Grid | Slack workspaces |
| GitHub and GitHub Enterprise | Repositories |
| Jira | Product access groups |
| Confluence | Product access groups |
| Google Drive | Directory groups |
| Gong | Workspaces |
| Microsoft Teams | Teams |
| OneDrive and SharePoint | Organization wide directory groups |
If a connector does not support source specific scope, include or exclude the entire connector. A profile only searches the connectors and scoped entities that an admin includes.
Use a profile with Gleanbot
Public Gleanbot responses use the Company knowledge profile. When an admin changes the profile, Glean propagates the changes to the identity used for public responses.
Private, user scoped experiences continue to use the requesting user . Public responses do not use a user's private credentials to retrieve content for a shared response.
For Slack setup and channel visibility, see Enable Public Mode.
Use a profile with auto-agents
When an agent builder configures an auto agent, they can choose how the agent searches for information:
- User data uses the permissions and personal context of the requesting user.
- Public data uses an administrator curated knowledge profile.
Public data agents are useful when the same bounded corpus must apply to everyone who can see the response.
Retrieve approved public documents
Some documents may be available to the organization in a connector but unavailable to a particular user because of how that connector represents permissions. A public data agent can retrieve approved documents through the identity of the profile without giving every user direct access in the source application.
The agent can only search the connectors, groups, repositories, workspaces, or teams included in the selected profile.
Share agents in multiplayer surfaces
People may share agents in Slack channels, collaborative workflows, and other surfaces where multiple people can see a response. User data retrieval can produce inconsistent results in these contexts because the agent may find content visible only to the person who started the run.
Configure the agent to use public data when the response should come from the same admin defined corpus for every viewer. For public or shared executions, Glean restricts user scoped authorization paths so the agent does not use the private credentials of the user in a shared response.
Troubleshoot retrieval
If a public data agent cannot find an expected document, check the following:
- The agent uses public data, not user data.
- The document's connector is included in the selected knowledge profile.
- The relevant workspace, repository, group, or team is included when the connector supports source specific scope.
- The document is indexed by Glean.
For connector-specific public-content rules, see What content Public Mode can use.
For more troubleshooting steps, see Troubleshoot document retrieval in agents.
See also
- Manage agent access—control who can use and share agents
- Knowledge Source Types—configure connectors, containers, and documents for agent steps
- Enable Public Mode—configure public replies in Slack