System Settings
System settings are cluster-wide keys that blueprints can read: the time zone, number and date formats, language rules, email defaults and your own values. A value marked secure stays hidden, and every request to view it is logged.
One place for cluster configuration
Some keys are predefined and documented below. Typical uses are email tokens, global reply-to addresses and global parameters for system components.
In a blueprint, read a setting with a static selection through value_get_system_key_select (get setting), or by a dynamic key through value_get_system_key (get dynamic setting).
Secure values stay hidden, and viewing them is logged
A secure value is not directly visible when you access system keys or review them in overviews or blueprints. Any request to view a secured setting is logged for the audit trail, so you can track who accessed which token and manage access and revocation.
For a service whose blocks read a service provider, use the provider instead: its value never enters a run at all.
These keys are predefined
Changing one alters the behaviour of the cluster. The System Settings Reference covers each key's example value and when to change it, secure token handling and a complete email configuration.
| Key | Description |
|---|---|
timezone |
The default timezone for the execution of date type blocks. |
thousand_separator |
The default separator for formatting thousands in numbers. |
decimal_separator |
The default separator for formatting decimals in numbers. |
language_user_enabled |
If true, the user's data determines their language preference. |
language_query_enabled |
If true, the data from the query determines the user's language. |
language_browser_enabled |
If true, the supported language in the browser determines the user's language. |
language_default |
The default language when the user's language cannot be determined or does not match a supported language. |
input_datetime_format |
The date format used in datetime inputs. |
input_date_format |
The date format used in date inputs. |
date_default_format |
The default date format when rendering dates in the user interface. |
default_divide_by |
The default number to divide pricing inputs by, for example 100 to store pricing fields in cents. |
email_default_from |
The default from address when sending emails. |
messagebird_originator |
The default originator name in MessageBird SMS for two-factor authentication (2FA). |
postmark_token |
The default server token when sending password reset emails. |
Next steps
System Settings Reference Every key with an example value, when to change it, and custom keys. Service Providers Credentials held by the cluster, so a key never sits on a pin.Frequently asked
What are RUAL system settings used for?
They are the centralized method for managing cluster-wide configuration parameters, from timezone and date formats to email tokens and global reply-to addresses. Blueprints read them through the get system setting block, either as static selections or as dynamic values.
How do I store a secret like an API token in RUAL?
Create the system setting as a secure value. It stays concealed when accessing system keys, in overviews and in blueprints, and any request to view a secured setting is logged for audit purposes, so you can track who accessed which token.
Which system settings does RUAL predefine?
Keys for timezone, thousand and decimal separators, the four language settings, date and datetime input formats, the default date rendering format, default_divide_by for pricing inputs, email_default_from, messagebird_originator and postmark_token.