Settings

Settings contains platform-wide configuration that administrators can review and update from the UI.

Open Administration > Settings.

Working With Settings

Settings are grouped by area. Each row shows:

• setting label
• setting key
• optional description
• current value
• default value

Users with update permission can edit a value and save it. Use Reset to remove the saved override and return to the displayed default value.

Secret settings use a secret-variable selector so the plaintext value is not shown.

Value Types

Settings can use different input types:

• boolean checkbox
• text field
• long text area
• integer field
• one-value-per-line list
• select field
• secret-variable selector

String-array settings accept one value per line. Empty lines are ignored when saving.

Mail SMTP encryption is selected from None, TLS, or SSL.

Saving one row updates that setting only. Validation errors are shown on the edited row.

Logging

The Logging group controls the minimum severity written to Ordyn's application and feature logs:

Setting	Deployment default
Application	LOG_LEVEL
Bridge	LOG_FEATURE_BRIDGE
Cache Sync	LOG_FEATURE_CACHE_SYNC
Jobs	LOG_FEATURE_JOBS
Malware Scan	LOG_FEATURE_MALWARE_SCAN
Package Discovery	LOG_FEATURE_PACKAGE_DISCOVERY
Performance	LOG_FEATURE_PERFORMANCE
Performance HTTP	LOG_FEATURE_PERFORMANCE_HTTP, or Performance when unset
Performance Queue	LOG_FEATURE_PERFORMANCE_QUEUE, or Performance when unset

The Application setting applies to the primary application file log. External log destinations retain their deployment configuration.

Select one of these levels, ordered from most verbose to most restrictive:

• Debug
• Info
• Notice
• Warning
• Error
• Critical
• Alert
• Emergency

The selected level and all more severe events are written. For example, Warning includes warning, error, critical, alert, and emergency events.

A value saved in Settings takes precedence over its deployment default. Reset removes the saved value. Performance HTTP and Performance Queue use their own deployment default when configured; otherwise, they inherit the effective Performance level.

Log-level changes can take up to 30 seconds to reach all running services. Restarting services is not required.

Debug can produce a large volume of output and may include sensitive operational details. Use verbose logging only for the time needed to investigate an issue and protect the resulting log files according to your organization's policies.

User Session Event Recording

audit.record_user_session_events controls whether Windows user logon and logoff events are added to endpoint History. It is disabled by default to avoid retaining user-session activity unless your organization's data-protection policy permits it.

This setting only controls History recording. Logon and logoff job triggers, configuration-profile checks, jitter, coalescing, and trigger variables continue to work when recording is disabled. Direct user information used while processing an unrecorded event is cleared when processing finishes.

Changing the setting affects events finalized afterward. Disabling it does not remove History entries that were recorded earlier; normal endpoint-history retention still applies to those entries.

The deployment default can be set with ORDYN_RECORD_USER_SESSION_EVENTS; an explicit value saved in Settings takes precedence.

Guidance

Change settings deliberately and document operational values outside Ordyn where your organization requires change control.

If a setting affects integrations, verify the integration after saving.