[Internal]: Update references to integration tiles UX #8153

Activity

1. github-actions

   added

   needs-teamIssues pending triage by the Docs TeamIssues pending triage by the Docs Team

   on Sep 1, 2026
2. github-actions commented on Sep 1, 2026

   

   github-actionsBot

   on Sep 1, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   Elastic Docs AI Menu

   Check one box to run an AI workflow for this issue.

   • Scope the docs work (docs-scope). Status: completed. View progress.

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

   👀React with 👀1Reacted by github-actions
3. jillguyonnet

   changed the title [-][Internal]:[/-] [+][Internal]: Update references to integration tiles UX[/+] on Sep 1, 2026
4. kosabogi

   added

   Team:SKIIssues owned by the SKI Docs TeamIssues owned by the SKI Docs Team

   and removed

   needs-teamIssues pending triage by the Docs TeamIssues pending triage by the Docs Team

   on Sep 7, 2026
5. bmorelli25

   assigned

   bmorelli25

   and

   vishaangelova

   on Oct 5, 2026
6. github-actions commented on Oct 13, 2026

   

   github-actionsBot

   on Oct 13, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   ✅ ScopeBot finished. https://github.com/elastic/docs-content/actions/runs/38403446522

   Generated from Gh Aw Issue Scope
7. github-actions commented on Oct 13, 2026

   

   github-actionsBot

   on Oct 13, 2026 – with GitHub Actions

   Contributor

   More actions

   🟢 ScopeBot Results: Full assessment

   Summary

   The merged Kibana change routes integration and input package tiles directly to the Add integration flow, adds an optional README callout and modal, and leaves content packages on their overview page. The Fleet and Security ingestion instructions describe steps that should be checked against this UX; the feature flag is disabled by default, so confirm its 9.6 availability before publishing the change.

   Request accuracy

   Accurate — the linked PR implements the described navigation change and confirms that it is behind a disabled-by-default feature flag.

   Recommended docs targets

   Page	URL	Action	Confidence	Why this page?
   Add an integration to an Elastic Agent policy	https://www.elastic.co/docs/reference/fleet/add-integration-to-policy	Update existing page	Medium	Its current steps say to select an integration and then click Add; the PR changes tile selection to route directly to the Add integration page and adds an optional README callout/modal. Confirm when the flag is enabled before describing this as the standard flow.
   Ingest data to Elastic Security	https://www.elastic.co/docs/solutions/security/get-started/ingest-data-to-elastic-security	Update existing page	Medium	Its “Find and add an integration” steps cover the Security onboarding route and describe selecting an integration before clicking Add. The PR says Security onboarding tiles are affected; align the steps with the direct route once the feature is enabled.

   How to tackle this

   1. Confirm whether the feature flag will be enabled for the 9.6 release and which deployments receive the change.
   2. Update the Fleet page to describe the direct route from an integration or input tile to Add integration, including the README callout/modal when available.
   3. Update the Security onboarding instructions for the same direct route. Preserve the content-package overview behavior and avoid implying every package has a README.

   Scope boundary

   The Observability host quickstart describes the Add Data → Host → Elastic Agent flow, not integration-tile selection, so it does not appear to need changes; check for a separate onboarding guide only if one documents tile clicks.

   Questions to go deeper

   • Will the feature flag be enabled by default in 9.6, and does availability differ by deployment type?
   • Does the Security guide’s “Find and add an integration” sequence describe the onboarding tiles changed by the PR, or a separate catalog route?
   • Is there an Observability onboarding guide that documents integration-tile clicks beyond the host quickstart?

   Generated from Gh Aw Issue Scope · ◷
8. vishaangelova

   linked a pull request that will close this issueUpdate Security integration steps for direct Add integration navigation #9056on Oct 27, 2026
9. vishaangelova

   added 3 commits that reference this issue on Nov 6, 2026

   Point integration steps to the Overview page section

   ...

   a40afda

   Point integration steps to the Overview page section and reword first…

   ...

   9454a95

   Make 'Add <integration>' steps work with direct Add integration navig…

   ...

   0e9cbb3
10. vishaangelova

    closed this as completedin #9252on Nov 6, 2026
11. vishaangelova

    reopened this on Nov 6, 2026