[vishaangelova]

Relates to #8153. Part of a set of PRs for this issue, split by docs set:

• #9055: the integration policy and agent policy pages, and a new page, Open an integration's details, that other pages link to
• #9056: Security pages
• This PR: Fleet and ingest pages
• #9252: Observability pages

The PRs don't depend on each other and can merge in any order. Close #8153 after all four merge.

Summary

Two UI changes affect the steps for adding an integration:

• Starting in 9.6 (and in Serverless), selecting an integration tile opens the Add page directly instead of the integration's details page (kibana#299010). This includes the tiles in Observability and Security onboarding, which use the same Fleet card logic.
• The Ready to add your first integration? page was removed in 9.3.6, 9.4.3, and 9.5.0 (kibana#271801). In earlier releases, it only appears on Elastic Cloud when no agents are enrolled yet, and never for a few integrations with their own setup flow, such as Elastic APM.

How the steps change

• "Click Add " becomes "If the integration's Overview page opens, click Add ." The next step is the same in every version, so there's no badge.
• The separate step that asked readers to read the integration's overview is removed on the stack monitoring pages, along with "Make sure you configure all required settings". The steps now match the other pages.
• "If the Ready to add your first integration? page opens, click Add integration only (skip agent installation)." This step has no applies_to badge on purpose. Even in the releases that still have it, the page only appears under the conditions above, so the step must stay conditional either way. Readers who don't see the page skip the step, and everyone reaches the same configuration page next. A badge would only add noise. Where this step was a tip or note, it's now a numbered step, because readers who see that page can't continue without it.
• The namespace index template and ILM pages go through the Installed integrations tab to reach the integration's Integration policies tab, because selecting a tile on Browse integrations now opens the Add page instead of the installed integration's pages.

Changes

8 pages: standalone agent policies, the Fleet-managed Kubernetes Helm example, namespace index templates and ILM, enabling a managed integration, Automatic Import, and stack monitoring for Elasticsearch and Kibana.

• Opening Integrations and finding the tile use the same wording as #9252, following the UI writing guide.
• Automatic Import: the step's purpose now comes after the conditional, so readers who skip the details page still know to configure the integration and assign it to an agent policy.
• The agent policies page, the Fleet API docs page, the standalone nginx examples, and Fleet Server on Kubernetes moved to #9055. They either link to its new page, Open an integration's details, or add the integration from an agent policy, which opens a flyout from 9.1.

Not changed: the Elastic GovCloud and Firehose pages, because those integrations still open their details page.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Tool(s) and model(s) used: Cursor with Claude Opus 5.5

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md
• deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md
• explore-analyze/ai-features/automatic-import.md
• manage-data/ingest/managed-integrations/enable-managed-integration.md
• reference/fleet/create-standalone-agent-policy.md
• reference/fleet/data-streams-namespace-custom.md
• reference/fleet/data-streams-namespace-ilm.md
• reference/fleet/example-kubernetes-fleet-managed-agent-helm.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[yetanothertw]

Admin docs changes look good, thank you!

[florent-leborgne]

LGTM