Home page - Only display features that a user has access to

[ryankeairns]

From issue #54192

---

I understand that disabling the home page is not on the roadmap.

However, there are parts of the UI which are pointless and annoying in certain situations.
In the case of a readonly user who has rights only for discovering indexes, what is the point of

• "Add data" on Home page: nothing can be done there
• "Manage" on Home page: it says "Application Not Found" anyway
• The whole "Ingest your data" section on Home page
• All the above applies also to Analytics / Overview

The best would be if these were hidden automatically based on user rights.
If it is problematic, there should be a way to hide them manually.

Originally posted by @balee in #54192 (comment)

[ryankeairns]

cc: @alexfrancoeur

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)

[elasticmachine]

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

[pgayvallet]

The best would be if these were hidden automatically based on user rights.

The features plugin is an xpack plugin, so we won't be able to leverage it from the home plugin. If we want to use user-right based check, we would have to directly use the uiCapabilities.

Now, the hardest part would be to find the capabilities we want to base all those restrictions on.

For example the manage your data section:

• /app/management/security/roles
• /app/monitoring
• /app/management/data/snapshot_restore
• /app/management/data/index_lifecycle_management

I'm not sure there is an uiCapability associated with accessing each of these apps/sections registered from OSS. (it's likely only registered via features in xpack)

cc @legrego as our features/capabilities expert 😅

[legrego]

Hmm, if these "Manage your data" items are showing up for underprivileged users, then that's a new bug for the respective teams. When I introduced #67791 / #77665 in 7.10, I took the time to make sure that the home screen was updated correctly based on user rights (It's all driven by UI Capabilities, which is available in OSS)

[ryankeairns]

Thanks for the feedback. I've asked the original poster to confirm which version of Kibana they were running.

[ryankeairns]

Thanks for the feedback. I've asked the original poster to confirm which version of Kibana they were running.

It was on v7.11.0. Sounds like we need to do some testing and validation before proceeding. I'll add this to ye ol' to-do list.

[Grunticus03]

Another use case where this causes usage issues/confusion is with the new feature, anonymous access. I have a dedicated space for anonymous user resources. While direct links are provided with interface features not shown (ie search bar, time filter, etc...), an enterprising user could easily strip the link down to the hostname and access the full interface and feature set allowed to the anonymous user. The space is currently configured to have everything disabled except dashboards in my case, but the Overview/Home pages are still visible.

[lukeelmers]

Ping @elastic/shared-ux