Manage action access

When you enable an action pack in Admin console → Platform → Actions, you can restrict which users or groups can invoke those actions in Chat and agents. This is called visibility scoping and is separate from who can configure actions in Agent Builder.

Two distinct access controls

Admin configurations control two entirely separate layers of access: who can use the action versus who can build with it.

Setting	What it controls	Where to configure
Visibility scope	Dictates which end users can see and invoke the action within Chat or agents	Admin console → Actions → Edit settings → Make available to
Role-based access	Dictates which admins and builders can view and add this action when constructing an agent	Admin console → Actions → Manage role-based access

This page covers visibility scope only. For builder-level access, see Managing action access.

How visibility scoping works

By default, when you enable an action pack, it's available to everyone in your Glean workspace. You can restrict this to specific users, departments, or groups.

End-user experience outside the visibility scope

If a user falls outside the visibility scope of an action but attempts to trigger it, the system behavior depends on the interface:

• In Glean: The action is completely hidden. It does not appear as an available tool, and Glean will ignore explicit user requests to invoke it.
• In Agents: If the agent is shared with the user, the specific action step fails silently. The agent will bypass the step and attempt to complete the remaining workflow.

Configure visibility scoping

1. Navigate to Glean Admin console.
2. Click Actions.
3. Click the action pack you want to configure and navigate to the Configuration tab.
4. Click Edit settings under Enable actions.
5. Under Make actions visible for all or some teammates, select either:
   • Agent
   • Chat
6. Under Access change the scope to:
   • All teammates
   • Specific department name
   • Specific teammate name
7. Click Save. The changes take effect immediately.

Recommended scoping by rollout stage

To ensure a secure and stable deployment, expand the visibility scope of your action progressively using the following phased approach:

Stage	Recommended scope
Initial pilot	Specific users — limit to your test group or IT and ops team
Departmental rollout	Specific departments — for example, Engineering only for Jira actions
Full rollout	Everyone

Visibility scope vs agent sharing

If an agent uses an action that's scoped to specific users, the action only executes successfully for users within that scope — even if the agent itself is shared more broadly.

warning

A Jira agent shared with the entire company but backed by a Jira Extension Actions pack scoped to Engineering only will fail the Jira action step for non-Engineering users. Either broaden the action's visibility scope or narrow the agent's sharing scope to match.

Troubleshooting

If a user reports that an action is available for some colleagues but not for them, check these three settings in order:

1. Visibility scope — the user's account or department isn't included in the Make available to setting.
2. Chat vs Agents toggle — the action is enabled for Agents only, not Chat. See Enabling actions for Chat vs Agents.
3. Individual action disabled — the specific action they need is unchecked within the pack. See Per-action enable/disable.

For questions and support, reach out to the Glean support team.