Settings Architecture Comparison
How our user and system settings structure compares to industry leaders.
Key Takeaway
All major, mature ERP systems enforce a strict separation between a user's personal settings (like language or theme) and the system-wide administrative configuration that affects all users. Our architecture now correctly follows this fundamental design principle.
Brix ERP (Our System)
- Separates identity ("My Profile") from preferences ("My Settings").
- User Settings (e.g., language) are stored in the user's profile and apply across devices.
- System-wide "Module Settings" are managed by administrators in a distinct area.
Odoo
- User-specific preferences (language, timezone, signature) are managed under the user menu.
- A separate, powerful "Settings" app is used by administrators to install modules and configure system behavior.
- Clear distinction between user personalization and system configuration.
SAP (S/4HANA - Fiori UX)
- User personalization (theme, default values) is done via the Fiori Launchpad's user actions menu.
- System configuration is a separate function performed by administrators using specific transaction codes (e.g., in the SPRO "Implementation Guide").
- Maintains a strong separation between user-facing settings and backend system configuration.
Oracle Fusion Cloud
- A "Settings and Actions" menu under the user icon allows for personalizations like language and accessibility.
- The "Setup and Maintenance" work area is the central hub for administrators and implementers to configure the entire application.
- Follows a clear model of separating user preferences from the functional setup of the system.