Skip to main content

Settings — Overview

Settings at /all-settings organizes configuration by category for the selected project. It does not have one universal field catalogue; groups and fields can vary with the project configuration.

Administrator access

The route and sidebar button require level 0, while the sidebar also excludes read-only classifications. The categories available to an eligible project can depend on returned configuration, installed plugins, and specialized-module prerequisites.

Open Settings​

  1. In the Dashboard sidebar, select Settings.
  2. Select a settings group, then choose the page you want to manage.
Settings navigation and configuration page in Dashboard

How Settings is organized​

Settings can group pages into general platform configuration, additional project configuration, plugin settings, and CMS/content-management settings. The exact groups, pages, labels, and order are runtime data; use the categories returned for the selected project rather than assuming a category is available.

Selecting a page updates the settings panel on the right. /all-settings resolves parent categories by key and version, then displays their ranked children. IDs, names, descriptions, configuration values, support links, and images are project data. A numeric category query selects an available category; named queries route to specialized modules.

The legacy /settings/basic and /settings/standard routes refer to this Settings overview. They do not establish a separate page, direct-route entitlement, merge, redirect, or replacement.

Work safely with a settings page​

  1. Select a category and verify that it belongs to the intended project and group.
  2. Treat every returned value, identifier, credential-like field, and support link as project data.
  3. Identify whether the category uses the generic buffered form or a specialized module.
  4. Do not assume a Save button is the only persistence boundary.
Platform-wide changes

Generic forms buffer changes, then submit configuration updates one at a time; partial completion is possible. Specialized modules can use immediate, debounced, create, delete, bulk, upload, provider, or external-navigation actions. Follow the approval process for the specific setting before making a change.

Accepted generic configuration updates can refresh global configuration state and invoke plugin hooks. Protected values may be masked by the API. Treat configuration values, credentials, provider data, and support links as sensitive, and use a project environment approved for configuration work.

Frequently asked questions​

Why is a category missing?​

Check the route and read-only gates, requested parent and child category trees, returned project configuration, installed plugins, and specialized-module prerequisites independently.

Why can’t I see the Save button?​

Generic lists show Save for pending buffered changes. Other modules can persist differently; review the action-specific guide and use a non-production project before making a change.

Related procedures: UUID access settings