settings-architecture

What problem does it solve?

Confusion and inconsistency about where configurable settings belong across the HBG Portal lead to duplicate controls, unexpected overrides, and maintenance friction; this guide provides a single decision framework to place settings correctly and avoid overlap.

Core Features & Use Cases

• Three configuration surfaces: clarifies ownership and content for Management Company, General Settings, and Admin Panel.
• Property override rules: specifies engine priority where property values override global defaults which fall back to hardcoded constants.
• Overlap prevention and decision tree: enforces single-editable locations, admin restrictions, and a step-by-step test for new settings placement.
• Practical references: maps to key implementation files and schema locations to guide engineers when adding or moving settings.
• Use case: determine whether a new revenue-share parameter belongs as a global default, a company assumption, or a property-level override and update the corresponding pages and schema.

Quick Start

Use the settings-architecture skill to determine where a new configuration belongs and update the corresponding UI page and schema references.