Sharing and Permissions
Who can share agents
You will be able to share your agents with others if:
- You are an Admin or Agent moderator
- Your Admin has set the default member permission "Can share and publish agents: On”
How to share an agent
In the Agent Builder, click on the Share button in the header. You will then be able to specify the access permissions for individuals, departments, and general users at your company.
Auto-generate agent description
When you share an agent that does not have a description, Glean automatically suggests an icon and an AI-generated description. You can review, edit, or replace the suggested description before confirming the share.
This feature helps keep the agent library organized and makes it easier for users to understand what each agent does. Descriptions remain optional—you can still share agents without one—but the auto-generation workflow reduces friction and encourages best practices.
To use auto-generated descriptions:
- Open the Agent Builder and click the Share button when you're ready to share your agent.
- If your agent doesn't have a description, a modal appears with a suggested icon and auto-generated description.
- Review, edit, or replace the suggested description.
- Confirm the share to save the description.
You can also use the Enhance button (sparkle icon) next to the description field in Agent Settings to generate or refine a description at any time, even after saving.
The table below shows the capabilities that are granted by each permission.
| No Access | Viewer | Editor | Owner | |
|---|---|---|---|---|
| See agent in the library | No | Yes | Yes | Yes |
| Run agent | No | Yes | Yes | Yes |
| View configuration of agent | No | Yes | Yes | Yes |
| Edit agent | No | No | Yes | Yes |
| Change permissions of agent | No | No | Yes | Yes |
| Delete agent | No | No | No | Yes |
| Add/remove other owners | No | No | No | Yes |
- You can grant the Editor or Owner permission to users that you want to collaborate with in building your agent. These users can edit your agent even if your admin did not give them the ability to create agents.
- Super admins and Admins have the Owner permission on all agents at the company.
- These permissions will be enforced everywhere, including if the agent is called via Slack or the API.
Document access across surfaces
The document access an agent uses depends on where it's invoked and how it's configured.
In the Glean web app, the agent uses the signed-in user's individual permissions. The agent can reference any document that the user has access to, so responses are personalized to each user.
In Slack, permissions depend on the visibility setting you choose when publishing the agent to Slack:
- Only visible to user (with or without the option to share): The agent uses the requesting user's individual permissions, similar to the web app experience.
- Visible to everyone in the channel: The agent applies a stricter access model. It only uses documents that are accessible to all members of the Slack channel, not just the person asking the question. This means documents that are restricted to specific people or groups won't be used by the agent, even if the person asking has access to them.
This stricter model is designed to prevent restricted documents from being inadvertently shared in a broader channel.
If an agent produces different or more limited responses in Slack compared to the web app:
- To align Slack behavior with the web experience, change the agent's Slack publishing setting to "Only visible to user" with an option to share. This lets the agent use each user's individual permissions.
- To keep responses visible to everyone, make sure the documents the agent references are shared broadly enough for all channel members to access. For details on what qualifies as broadly shared content, see Publishing to Slack.
Publishing options
The Share panel will expose additional publishing options. These will only appear if they are relevant to the agent:
- Slack (agents with chat message triggers only): Publishing an agent to Slack enables users to interact with the agent directly within Slack, allowing the agent to respond to messages, perform tasks, or provide information in Slack channels.
- API: Publishing an agent via API exposes the agent’s capabilities programmatically, letting other software systems invoke the agent’s logic and receive results, which enables integrations with custom workflows or external applications.
- Embed: Embedding an agent allows users to insert the agent’s interface or functionality into other web pages or platforms, so users can interact with the agent outside of Glean, such as on internal portals or knowledge bases.