Enabling or disabling individual actions within a pack

When you add an action pack in Admin console → Platform → Actions, all actions in the pack are enabled by default. You can selectively disable individual actions to control exactly which operations are available to users in Assistant and to agents.

Why you'd do this

Action packs bundle related operations together, but not every operation may be appropriate to expose. For example, the Jira action pack includes both read actions (Search issues, Get issue details) and write actions (Create issue, Create comment, Edit issue). You might want to enable read actions immediately while holding off on write actions until your team has tested them.

Common scenarios:

• Enable search and read actions only during a pilot rollout.
• Disable destructive actions (delete, close, archive) permanently.
• Enable a subset of actions for Assistant but a broader set for agents.
• Temporarily disable a specific action while a bug is being resolved.

Configuration steps

1. Navigate to Glean Admin console.
2. Click Platform → Actions.
3. Click the action pack you want to configure and go to the Configuration tab.
4. Click Edit settings under Enable actions.
5. Expand the Agents section to see the full list of individual actions available to agents.
6. Expand the Assistant section to see the list available in Assistant.
7. Uncheck any actions you want to disable.
8. Click Save.

note

The Agents and Chat sections are configured independently. Disabling an action in the Agents section doesn't automatically disable it in Chat, and vice versa. For more on this distinction, see Enabling actions for Chat vs Agents. The Agents and Assistant sections are configured independently. Disabling an action in the Agents section doesn't automatically disable it in Chat, and vice versa. For more on this distinction, see Enabling actions for Chat vs Agents.

Read vs. write actions — recommended starting point

Action type	Examples	Recommended default
Read	Search, Get, List, Fetch	Enable immediately
Write	Create, Update, Edit, Post	Enable after testing
Destructive	Delete, Close, Archive, Remove	Disable unless explicitly needed

Changes take effect immediately

Enabling or disabling an individual action takes effect immediately — no re-crawl, restart, or re-authentication is needed. Active agent runs that have already started a step complete it; the change applies to new invocations only. Enabling or disabling an individual action takes effect immediately — No re-crawl, restart, or re-authentication is needed. Active agent runs that have already started a step complete it; the change applies to new invocations only.

Difference from action pack-level enable/disable

Disabling an individual action within a pack is different from disabling the entire pack:

Scope	What it affects
Individual action disabled	Only that specific operation is unavailable; the rest of the pack continues to work.
Entire pack disabled	All actions in the pack become unavailable across Chat and Agents.
Entire pack disabled	All actions in the pack become unavailable across Assistant and agents.
To disable the entire pack, use the toggle at the top of the action pack card rather than unchecking individual actions.

For any further issues or queries, reach out to the Glean support team.