vendix-settings-system

Centralize store and organization settings in a NestJS multi-tenant application by standardizing configurations through a dual defaults pattern, using hardcoded defaults alongside database templates for reliable governance. This ensures consistent branding and template usage across tenants.

The dual defaults pattern for managing Vendix settings combines hardcoded default values with database-driven templates. This approach provides administrators flexible control over default configurations while ensuring baseline settings always exist for backend and frontend synchronization.

Add new settings sections using Prisma-backed services by following step-by-step guidance to update defaults and apply templates. You interact with the standardized configuration system to ensure new sections integrate correctly with the multi-tenant governance structure.

Vendix settings management supports frontend and backend synchronization by serving as a source-of-truth for branding and defaults. Settings APIs fetch and update values consistently across the stack, ensuring both layers reflect the current configuration.

The APIs used to fetch and update store and organization settings include GET /store/settings, PATCH /store/settings, GET /organization/settings, and PUT /organization/settings. These endpoints manage values within the centralized multi-tenant configuration system.

You can use default templates to manage administrator configurations in a multi-tenant environment. The system implements a dual defaults pattern allowing administrators to override hardcoded values with database templates for flexible governance.