Share Skills

Admins can share Skills with wider audiences beyond individual teammates. When you share a Skill at the department or organization level, you determine who can access that Skill and whether to automatically enable it for recipients.

Sharing one Skill doesn't change who can create Skills or the workspace usage audience. See Set up Skills and manage access.

Glean scans a Skill uploaded locally, or imported from a third-party repository, when its instructions or files change, including when you publish it. Skills from Glean are safe by default and aren't scanned. See Skill scanning and safety review.

Sharing grants access to a Skill, while enablement controls whether an individual user can invoke it.

Because these settings operate independently:

• Recipients with access can continue using a shared Skill even if the creator disables it for their own account.
• Creators who disable a Skill cannot invoke it until they re-enable it.

Share a Skill from the Admin console

Admins can share Skills from the Admin console management interface.

1. Navigate to Admin console → Skills.

2. Go to the Manage tab.

3. Locate the Skill you want to share or manage.

4. Click the context menu (three dots) and select Share.

5. In the share dialog, configure the following:

   People with access:

   • Add individual teammates, departments, or groups who should have access.
   • The Skill creator is the Owner and can't be changed from this dialog.

   General access:

   • Choose from the dropdown:
     • Restricted to people with access — only the people, departments, and groups in People with access can use the Skill.
     • Anyone at [Company] with the link can view — anyone in the organization can find and use the Skill.

   Advanced settings (admins and Skills Moderators only):

   • Auto-enable — when checked, Assistant automatically triggers this Skill when relevant. Teammates can turn it off anytime.

6. Click Save.

To modify access later, open the same dialog and update the people, general access, or Auto-enable settings. Changes take effect immediately, and teammates removed from the audience lose access on their next session. For the user-side sharing procedure, see Sharing Skills.

note

Admins can also enable or disable Auto-enable for any Skill directly from the Manage tab's table without opening the share dialog.

Modify access level

When sharing a Skill, you assign an access level to each recipient or group:

• Viewer — can use the Skill.
• Editor — can use and edit the Skill.

The Skill creator is the Owner. Owner is set automatically and can't be assigned from the share dialog.

To change someone's access level:

1. Navigate to Admin console → Skills → Manage.
2. Locate the Skill you want to modify access to.
3. Click the context menu (three dots) for the Skill and select Share.
4. Find the person or group in the People with access section.
5. Click the dropdown next to their name showing their current access level.
6. Select the new access level (Viewer or Editor).
7. Click Save.

Delete a shared skill

Your capability to delete a Skill depends on both your assigned role and where the Skill is shared:

Role	What You Can Delete	How / Notes
Owner	Any Skill you created	Delete directly from the Skill options
Editor	None	You can use and edit shared Skills, but cannot delete them
Admin	Any organization-shared Skill	Go to Admin console → Skills → Manage (Excludes private Skills without recipients)
Skills Moderator	Organization-shared Skills in your assigned scope	Go to Admin console → Skills → Manage

If you don't have permission to delete a Skill, contact the Skill's owner, an Admin, or a Skills Moderator.

For full details, see Skills roles and permissions.

If you can't delete a Skill, contact its owner or an admin or Skills Moderator. See Skills roles and permissions.

Skill recipient experience

When a Skill is shared with users:

• The Skill appears in the recipient's Shared tab under Settings → Skills.
• If you selected Auto-enable when sharing, the Skill is automatically enabled and ready to use.
• Recipients can see the Skill creator and the date the Skill was created.
• Recipients can enable or disable any Skill at any time from their Skills settings, including auto-enabled Skills.
• A recipient must keep the Skill turned on for Assistant to invoke it for their queries.
• When the creator turns the Skill off for themselves, it remains available to recipients who have access and have it turned on. The creator can't invoke it until they turn it on again.
• Recipient enablement does not override access or safety controls. Security-blocked Skills remain unavailable.
• Recipients are notified by email when the Skill is shared with them and when the owner updates it. Glean sends at most one update email per Skill per day, so frequent edits don't generate multiple notifications.

Sharing best practices

• Start restricted, then expand: Share new Skills with a small group first, validate they work as expected, then expand to broader audiences
• Use auto-enable thoughtfully: Auto-enable is useful for Skills that enhance core workflows, but avoid over-enabling to prevent Skill overload
• Document Skill purpose: Ensure Skill descriptions clearly explain when and how the Skill should be used so recipients understand its value
• Review sharing regularly: Periodically audit which Skills are shared at what scope to ensure alignment with current team structures and needs