Skip to content

Commit 59d7006

Browse files
authored
Update explore-analyze/manage-access-to-ai-assistant.md
1 parent 4f14c7a commit 59d7006

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

explore-analyze/manage-access-to-ai-assistant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The **GenAI Settings** page has the following settings:
3838
- **Default AI Connector**: Use this setting to specify which connector is selected by default when you access AI-powered features. Default setting: **No default connector**.
3939
- If **No default connector** is selected, AI-powered features will default to the connector that was most recently used in your environment.
4040
- If **Elastic Managed LLM** or a custom LLM connector is selected, AI-powered features will default to that connector regardless of which connector was used most recently in your environment.
41-
- **Disallow all other connectors**: When this setting is disabled, whenever you use an AI-powered feature you can select which connector should power it. Enable it to prevent connectors other than the default connector specified above from being used in your space. Default setting: disabled.
41+
- **Disallow all other connectors**: When this setting is disabled, whenever you use an AI-powered feature you can select which connector should power it. Enable it to prevent connectors other than the default connector from being used in your space. Default setting: disabled.
4242
- **AI feature visibility**: This button opens the current Space's settings page, where you can specify which features are enabled in your environment, including AI-powered features.
4343
- **AI Assistant visibility**: This setting allows you to choose which AI Assistants are available to use and where. There are several options:
4444
- **Only in their solutions** (default): The Security AI Assistant appears in {{elastic-sec}}, and the {{obs-ai-assistant}} appears in {{es}} and {{observability}}.

0 commit comments

Comments
 (0)