Global Settings

This section covers the configuration of global application settings in Prodly. Administrators can manage site details, default credit allocations, and plan‑specific parameters from a single interface.

Overview

The Global Settings page provides a centralised way to edit all system‑wide configuration values. Settings are stored in the database and can be updated on the fly without redeploying the application.

Changes made here affect the entire platform – including the site name shown in the browser tab, the default number of credits for new users, and the limits associated with each subscription plan.

Available Settings

Settings are automatically grouped into logical categories based on their keys. The following groups are currently defined:

General – Contains basic site information and global defaults.
Examples: site_name, site_description, default_credits.
Free Plan – Configuration for the free tier, such as the number of credits granted and any feature limits.
Pro Plan – Parameters for the professional subscription plan.
Other – Any settings that do not fall into the above groups are collected here.

The exact list of settings depends on the records present in the settings table. Each setting has a key, a value, and a description that explains its purpose.

Managing Settings in the Admin Panel

Navigate to the Settings page

Go to Admin Panel → Settings from the main dashboard.

Edit the values

Each setting is displayed with its label (derived from the key) and description. Modify the input fields as needed.

Save your changes

Click the Save All button at the top or bottom of the page. Only modified settings will be sent to the server.

Verify the update

A success toast notification confirms the number of updated settings. The interface also shows the last update timestamp for each setting (if available).

Technical Details

Data storage: All settings live in the settings database table with columns key, value, description, updated_at, and updated_by.
API endpoints:
- GET /api/admin/settings – retrieves the full list of settings.
- PATCH /api/admin/settings – updates a single setting (expects { key, value } in the request body).
Client‑side behaviour:
The page compares current values with the original ones to enable/disable the Save All button.
When a setting like site_name is updated, a custom siteNameUpdated event is dispatched, allowing other parts of the application to react to the change.

Ensure that sensitive values (e.g., SMTP passwords) are handled securely and are never exposed to the client.