Skip to main content

SettingsStoreFieldConfig

Configuration for a settings store field, defining how it should be stored, scoped, validated, and accessed.

Signature

name

propertystring

The name of the field. This will be combined with the namespace to create the full key (e.g., 'dashboard.theme').

scope

Function that determines how this field should be scoped. Defaults to global scoping (no isolation).

readonly

propertyboolean
Default:false

Whether this field is readonly via the GraphQL API. Readonly fields can still be modified programmatically via a service.

requiresPermission

property| Array<Permission | string> | Permission | string | { read?: Array<Permission | string> | Permission | string; write?: Array<Permission | string> | Permission | string; }v3.5.0 - Added support for object with read/write properties

Permissions required to access this field. If not specified, basic authentication is required for admin API access.

Can be either:

  • A single permission or array of permissions (applies to both read and write)
  • An object with read and write properties for granular control

Example

Ts

validate

property( value: any, injector: Injector, ctx: RequestContext, ) => string | LocalizedString[] | void | Promise<string | LocalizedString[] | void>

Custom validation function for field values.

Was this chapter helpful?
Report Issue
Edited Feb 25, 2026ยทEdit this page