Skip to content

Clarify branding inheritance behavior after customization #6293

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.

Sign up for GitHub

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

Merged
pavinduLakshan merged 2 commits into from
Jul 30, 2026
Merged

Clarify branding inheritance behavior after customization #6293

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d3a0576
Clarify branding inheritance behavior after customization
pavinduLakshan Jul 29, 2026
56a9d66
Address review comments
pavinduLakshan Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ...organization-management/inheritance-in-organizations/ui-branding-inheritance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,9 @@

- Organizations can customize their own branding settings, overriding the inherited settings. These overridden settings then pass down to the organization’s descendants.

!!! note "Customized branding does not track later ancestor changes"
Once an organization customizes its branding, it stops inheriting from its ancestors. Any branding changes made later at an ancestor level are **not** propagated to it; the organization keeps using its own customized settings independently. This continues until the organization reverts its branding, at which point it resumes inheriting from the nearest ancestor with custom settings.

- Organizations can also revert their branding settings, restoring the inherited values.

### Application-specific branding
Expand All @@ -36,6 +39,9 @@

- Organizations can customize their own application-specific branding settings, overriding either their organization-wide settings or the inherited settings. These overridden settings then pass down to the organization’s descendants.

!!! note "Customized branding does not track later ancestor changes"
Once an organization customizes its application-specific branding, it stops inheriting from its ancestors for that application. Any branding changes made later at an ancestor level are **not** propagated to it; the application keeps using its own customized settings independently. This continues until the application-specific branding is reverted, at which point it resumes using the organization’s own organization-wide branding if available, or otherwise inherits from the nearest ancestor.

Check warning on line 43 in en/includes/guides/organization-management/inheritance-in-organizations/ui-branding-inheritance.md

View workflow job for this annotation

GitHub Actions / Vale style check 

[vale] reported by reviewdog 🐶
[WSO2-IAM.SentenceLength] Try to keep sentences short (< 30 words).

Raw Output:
{"message": "[WSO2-IAM.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "en/includes/guides/organization-management/inheritance-in-organizations/ui-branding-inheritance.md", "range": {"start": {"line": 43, "column": 291}}}, "severity": "INFO"}

Comment thread
coderabbitai[bot] marked this conversation as resolved.
- Organizations can also revert application-specific branding settings. When reverted, the application uses the organization’s custom branding settings. If the organization has no custom branding, it inherits the branding from the nearest parent organization in the hierarchy that has custom settings.

!!! note "Reverting affects the entire branding configuration"
Expand Down
Loading