docs: tag Kibana custom branding availability on serverless (#8195) - #8190
Open
florent-leborgne wants to merge 2 commits into
Open
docs: tag Kibana custom branding availability on serverless (#8195)#8190florent-leborgne wants to merge 2 commits into
florent-leborgne wants to merge 2 commits into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
florent-leborgne
commented
Sep 3, 2026
florent-leborgne
marked this pull request as ready for review
September 3, 2026 21:10
Contributor
Docs review summaryFocus areas
Nits
Notes
|
shainaraskas
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Identified by @nastasha-solomon's eagle eyes - part of the settings became available in serverless earlier this summer and only the advanced settings page got updated.
This PR addresses #8195 with the following changes:
deploy-manage/kibana-custom-branding.md: Marks the page as available on serverless, tags Page title as serverless-unavailable, and drops deployment-only wording from the intro so the steps match Elastic Stack and Elastic Cloud Serverless.The companion Advanced Settings reference in
elastic/kibana(docs/reference/advanced-settings-global.yml) already tags the same split: logo, organization name, and both favicons are serverless GA, andxpackCustomBranding:pageTitleis serverless unavailable. No Kibana companion PR is needed.Source: serverless allowlist in
src/platform/packages/shared/serverless/settings/common/index.ts(added in elastic/kibana#279246). Page title is not on that list or any project-specific allowlist.Resolves
Closes #8195