Improve the the custom home route feature

[ryankeairns]

Currently, a custom route can be set per Space and this determines the page a user of that Space will land on upon logging in. However, if you click on the Home link (in the left nav) or Elastic cluster logo (in the header) you will land on the default Elastic console home page.

This was surprising to me (I actually thought the custom route didn't take) as my expectation was for the home link/logo button to honor the setting. My instinct is that this expectation is shared by a good number of users, but that assumption should be verified. This issues serves as a place to collect feedback over time in order to make that validation prior to proceeding with additional thought and action.

---

See related comment by @alexfrancoeur in #25734 (comment)

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[pgayvallet]

Just some technical pointers in case we decide to perform any change:

kibana/src/core/public/chrome/ui/header/header.tsx

Lines 121 to 122 in 523cd0f

	<HeaderLogo
	href={homeHref}

kibana/src/core/public/chrome/chrome_service.tsx

Line 224 in bb4e0cc

homeHref={http.basePath.prepend('/app/home')}

[lucabelluccini]

If this will be implemented, it would be nice to have 2 options:

• Customizing the destination link
• Disable the Home link

[parkmisoo]

My Basic license is activing

I cant find the chrome directory
I just set

I dont know why is not set

To find the chrome directory
please tell me how to set

[pgayvallet]

@parkmisoo What are you trying to achieve here exactly? Is this related to the issue at stake here?

[pgayvallet]

Navigation changed a lot over the past few years, I'll assume the issue is out of date and close it.