Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more clarity about Kibana Custom Branding that requires an Enterprise subscription #198701

Open
jeanfabrice opened this issue Nov 1, 2024 · 2 comments
Labels
Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@jeanfabrice
Copy link

jeanfabrice commented Nov 1, 2024

Describe the feature:
In Kibana, the Advanced Setting section "Custom Branding" appears with any kind of license (Basic, Gold, Platinum, Enterprise, etc)
Image

The "subscription required" link in the description text of the setting takes the user to a pretty generic landing page, which may create confusion.

As a user with a Free or Platinum subscription, I have access to these Kibana advanced settings:
I can upload a logo, see it rendered on the setting page, but I can't see it on Kibana Home page

The suggested feature is to completely hide the settings to the user when the current subscription is not compatible with Custom Branding / Custom Banner (as per https://www.elastic.co/subscriptions#service-54):
Image

As a workaround, we can:

  • improve the landing page (current: https://www.elastic.co/subscriptions) to redirect the user exactly to the Custom Branding / Custom Banner subsection
  • If changing the link test is also an option, then using "Enterprise Subscription required" (for Custom branding) and "Platinum subscription required" (for Custom banner) in place of "Subscription required" would also help, as "Free" and "Gold" are also a valid subscriptions, that falls under the "Subscription required" terms

Describe a specific use case for the feature:
Not confuse the user with a feature that is not available for his subscription license

@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 1, 2024
@tsullivan tsullivan added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Nov 1, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-sharedux (Team:SharedUX)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 1, 2024
@sebelga
Copy link
Contributor

sebelga commented Nov 2, 2024

We could work this issue along with #196659 as they are related in terms of showing/hidding sections based on the active user or space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

No branches or pull requests

4 participants