Skip to content

[Internal]: New AI section in Stack Management & AI assistant navigation header selectorΒ #3268

@rbrtj

Description

@rbrtj

Description

We're introducing a new AI section in Stack Management. This moves all AI Assistant management pages out of the Kibana section and into the new AI section.
Along with the new AI section, we're also introducing a GenAI Settings page to manage general configurations such as connectors and feature visibility. Additionally, the AI Assistant Visibility setting has been moved to the GenAI Settings page (previously under Kibana -> Advanced Settings). This setting has been removed from the Serverless and ECH Solution views.

Image

We've also added a new navigation header selector for non-solution pages (such as Analytics, Stack Management, etc.), allowing users to choose which version of the Assistant they want to see. Based on their selection, the AI Assistant Visibility setting is updated, and the relevant Assistant window opens instantly. After selecting an Assistant, the button to open the chosen Assistant version will persist in the navigation header.

Screen.Recording.2025-09-19.at.11.41.41.mov

Resources

These features were implemented in:
elastic/kibana#227289
elastic/kibana#233727
As part of Elastic AI Assistant improvements: https://www.figma.com/design/qtLNAkFbtcL8TGSVzVUPw1/-Shared--GenAI-Settings?node-id=4375-12297&p=f&t=R1DJ21MX0L64ge1f-0

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

New AI Section -> All
New header selector -> On-prem and Cloud hosted (non-solution view spaces). The setting is unavailable in serverless.

What release is this request related to?

9.2

Serverless release

It is already released in Serverless

Collaboration model

The documentation team

Point of contact.

Main contact:
@rbrtj
@isaclfreire
@peteharverson

Stakeholders:

Metadata

Metadata

Labels

Team:ExperienceIssues owned by the Experience Docs Team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions