[9.4] [SecuritySolution][Navigation] Fix launchpad order in classic global nav (#268216) (#268466)

# Backport

This will backport the following commits from `main` to `9.4`:
- [[SecuritySolution][Navigation] Fix launchpad order in classic global
nav (#268216)](#268216)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-05-08T14:18:11Z","message":"[SecuritySolution][Navigation]
Fix launchpad order in classic global nav (#268216)\n\n> [!Note] \n>
`9.4.1` FF day is 8th of May so it should be merged today,
preferably\n\n## Summary\n\nThe launchpad item is below `Manage` item on
the classic global sidenav\ninstead of above it. This PR fixes that and
moves it above `Manage` just\nlike it is in the Security Solution
classic nav.\n\n<details><summary>Current Security Solution classic
nav</summary>\n<img width=\"250\" height=\"721\" alt=\"Screenshot
2026-05-07 at 11 36
20\"\nsrc=\"https://github.com/user-attachments/assets/7a34b2a0-a6e3-4b38-8952-136ba432a436\"\n/>\n</details>
\n\n<details><summary>Current global side nav</summary>\n<img
width=\"265\" height=\"1135\" alt=\"Screenshot 2026-05-07 at 16 58
03\"\nsrc=\"https://github.com/user-attachments/assets/d7d50cf0-be9b-42e9-832c-25327e068598\"\n/>\n</details>
\n\n<details><summary>Fixed global side nav</summary>\n<img
width=\"293\" height=\"1161\" alt=\"Screenshot 2026-05-07 at 17 00
49\"\nsrc=\"https://github.com/user-attachments/assets/8b0092f5-0a00-4ee6-a7da-e3184c71f774\"\n/>\n</details>
\n\nrelated to https://github.com/elastic/kibana/pull/260429/\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"2dd76a3ab03c1353df725e26e8188b72e6450014","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:version","v9.4.0","v9.5.0","Team:Security
Deployment","v9.4.1"],"title":"[SecuritySolution][Navigation] Fix
launchpad order in classic global
nav","number":268216,"url":"https://github.com/elastic/kibana/pull/268216","mergeCommit":{"message":"[SecuritySolution][Navigation]
Fix launchpad order in classic global nav (#268216)\n\n> [!Note] \n>
`9.4.1` FF day is 8th of May so it should be merged today,
preferably\n\n## Summary\n\nThe launchpad item is below `Manage` item on
the classic global sidenav\ninstead of above it. This PR fixes that and
moves it above `Manage` just\nlike it is in the Security Solution
classic nav.\n\n<details><summary>Current Security Solution classic
nav</summary>\n<img width=\"250\" height=\"721\" alt=\"Screenshot
2026-05-07 at 11 36
20\"\nsrc=\"https://github.com/user-attachments/assets/7a34b2a0-a6e3-4b38-8952-136ba432a436\"\n/>\n</details>
\n\n<details><summary>Current global side nav</summary>\n<img
width=\"265\" height=\"1135\" alt=\"Screenshot 2026-05-07 at 16 58
03\"\nsrc=\"https://github.com/user-attachments/assets/d7d50cf0-be9b-42e9-832c-25327e068598\"\n/>\n</details>
\n\n<details><summary>Fixed global side nav</summary>\n<img
width=\"293\" height=\"1161\" alt=\"Screenshot 2026-05-07 at 17 00
49\"\nsrc=\"https://github.com/user-attachments/assets/8b0092f5-0a00-4ee6-a7da-e3184c71f774\"\n/>\n</details>
\n\nrelated to https://github.com/elastic/kibana/pull/260429/\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"2dd76a3ab03c1353df725e26e8188b72e6450014"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/268216","number":268216,"mergeCommit":{"message":"[SecuritySolution][Navigation]
Fix launchpad order in classic global nav (#268216)\n\n> [!Note] \n>
`9.4.1` FF day is 8th of May so it should be merged today,
preferably\n\n## Summary\n\nThe launchpad item is below `Manage` item on
the classic global sidenav\ninstead of above it. This PR fixes that and
moves it above `Manage` just\nlike it is in the Security Solution
classic nav.\n\n<details><summary>Current Security Solution classic
nav</summary>\n<img width=\"250\" height=\"721\" alt=\"Screenshot
2026-05-07 at 11 36
20\"\nsrc=\"https://github.com/user-attachments/assets/7a34b2a0-a6e3-4b38-8952-136ba432a436\"\n/>\n</details>
\n\n<details><summary>Current global side nav</summary>\n<img
width=\"265\" height=\"1135\" alt=\"Screenshot 2026-05-07 at 16 58
03\"\nsrc=\"https://github.com/user-attachments/assets/d7d50cf0-be9b-42e9-832c-25327e068598\"\n/>\n</details>
\n\n<details><summary>Fixed global side nav</summary>\n<img
width=\"293\" height=\"1161\" alt=\"Screenshot 2026-05-07 at 17 00
49\"\nsrc=\"https://github.com/user-attachments/assets/8b0092f5-0a00-4ee6-a7da-e3184c71f774\"\n/>\n</details>
\n\nrelated to https://github.com/elastic/kibana/pull/260429/\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...","sha":"2dd76a3ab03c1353df725e26e8188b72e6450014"}}]}]
BACKPORT-->

Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>

Author: kibanamachine

x-pack/solutions/security/plugins/security_solution/public/app/links/app_links.ts

@@ -89,7 +89,7 @@ export const getFilteredLinks = async (
     assetInventoryLinks,
     rulesLinks,
     siemMigrationsLinks,
-    managementFilteredLinks,
     launchPadLinks,
+    managementFilteredLinks,
   ]);
 };

x-pack/solutions/security/plugins/security_solution/public/management/links.ts

@@ -95,7 +95,7 @@ export const links: LinkItem = {
   path: MANAGE_PATH,
   skipUrlState: true,
   hideTimeline: true,
-  globalNavPosition: 12,
+  globalNavPosition: 13,
   capabilities: [SECURITY_UI_SHOW_PRIVILEGE],
   globalSearchKeywords: [
     i18n.translate('xpack.securitySolution.appLinks.manage', {

x-pack/solutions/security/plugins/security_solution/public/onboarding/links.ts

@@ -39,6 +39,7 @@ export const launchPadLinks: LinkItem = {
   id: SecurityPageName.launchpad,
   title: LAUNCHPAD,
   path: ONBOARDING_PATH,
+  globalNavPosition: 12,
   globalSearchKeywords: [
     i18n.translate('xpack.securitySolution.appLinks.launchpad', {
       defaultMessage: 'Launchpad',

x-pack/solutions/security/plugins/security_solution/public/siem_migrations/links.ts

@@ -95,7 +95,6 @@ export const links: LinkItem = {
   ],
   links: subLinks,
   skipUrlState: true,
-  globalNavPosition: 13,
   categories: [
     {
       label: i18n.translate('xpack.securitySolution.appLinks.category.automaticMigrations', {

x-pack/solutions/security/plugins/security_solution/public/siem_readiness/links.ts

@@ -13,7 +13,6 @@ import type { LinkItem } from '../common/links/types';
 
 export const siemReadinessLinks: LinkItem = {
   capabilities: [[`${SECURITY_FEATURE_ID}.show`]],
-  globalNavPosition: 13,
   globalSearchKeywords: [
     i18n.translate('xpack.securitySolution.appLinks.siem_readiness', {
       defaultMessage: 'SIEM Readiness',