Clarify that branding revert applies to the whole configuration, not individual fields#6248
Conversation
…individual fields
📝 WalkthroughWalkthroughChangesUI branding inheritance
Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@en/includes/guides/organization-management/inheritance-in-organizations/ui-branding-inheritance.md`:
- Around line 41-48: Rewrite the individual-field limitation in the note
beginning “Reverting applies to the whole configuration...” using active voice:
replace “an individual setting ... cannot be reverted on its own” with wording
such as “You cannot revert an individual setting on its own,” while preserving
the surrounding meaning and guidance.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: fe7043ac-cbcb-4142-8dc3-0b3e6352659d
📒 Files selected for processing (1)
en/includes/guides/organization-management/inheritance-in-organizations/ui-branding-inheritance.md
| !!! note "Reverting applies to the whole configuration, not individual fields" | ||
| Reverting restores inherited values for the **entire** branding customization saved at | ||
| that level — an individual setting (for example, just the logo) cannot be reverted on | ||
| its own. Clearing the value of a single field and saving does not cause that field to | ||
| inherit from the parent level; the level's customization remains in effect with that | ||
| field left empty. To restore inheritance, use **Revert to default**, as described in | ||
| [Configure UI branding]({{base_path}}/guides/branding/configure-ui-branding/#revert-branding). | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use active voice for the individual-field limitation.
Replace “an individual setting ... cannot be reverted on its own” with direct wording such as “You cannot revert an individual setting on its own.” This keeps the note concise and follows the documentation requirement to prefer active voice.
Suggested wording
- that level — an individual setting (for example, just the logo) cannot be reverted on
- its own. Clearing the value of a single field and saving does not cause that field to
+ that level — you cannot revert an individual setting (for example, just the logo) on
+ its own. Clearing the value of a single field and saving does not cause that field to📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| !!! note "Reverting applies to the whole configuration, not individual fields" | |
| Reverting restores inherited values for the **entire** branding customization saved at | |
| that level — an individual setting (for example, just the logo) cannot be reverted on | |
| its own. Clearing the value of a single field and saving does not cause that field to | |
| inherit from the parent level; the level's customization remains in effect with that | |
| field left empty. To restore inheritance, use **Revert to default**, as described in | |
| [Configure UI branding]({{base_path}}/guides/branding/configure-ui-branding/#revert-branding). | |
| !!! note "Reverting applies to the whole configuration, not individual fields" | |
| Reverting restores inherited values for the **entire** branding customization saved at | |
| that level — you cannot revert an individual setting (for example, just the logo) on | |
| its own. Clearing the value of a single field and saving does not cause that field to | |
| inherit from the parent level; the level's customization remains in effect with that | |
| field left empty. To restore inheritance, use **Revert to default**, as described in | |
| [Configure UI branding]({{base_path}}/guides/branding/configure-ui-branding/#revert-branding). |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@en/includes/guides/organization-management/inheritance-in-organizations/ui-branding-inheritance.md`
around lines 41 - 48, Rewrite the individual-field limitation in the note
beginning “Reverting applies to the whole configuration...” using active voice:
replace “an individual setting ... cannot be reverted on its own” with wording
such as “You cannot revert an individual setting on its own,” while preserving
the surrounding meaning and guidance.
Source: Coding guidelines
✅ Fix VerificationYou can view the update on the page
|
|
|
||
| - Organizations can also revert their application-specific branding settings, restoring either their organization-wide settings or the inherited values. | ||
|
|
||
| !!! note "Reverting applies to the whole configuration, not individual fields" |
There was a problem hiding this comment.
| !!! note "Reverting applies to the whole configuration, not individual fields" | |
| !!! note "Reverting affects the entire branding configuration" |

Purpose
Clarifies the UI branding inheritance guide to make explicit that reverting branding restores inherited values for the entire configuration saved at a level (via Revert to default), not for an individual field in isolation. Clearing a single field's value (e.g. the Logo URL) and saving does not cause that field alone to inherit — the level's customization stays in effect with that field left empty.
Related to wso2/product-is#28091, where a customer expected clearing an individual field to trigger inheritance for that field.