Operator guideEN

System Settings / Detail

Configurator guide for the dynamic Core system settings editor, with detailed CRM Docs, Identity Graph, and marketing-events field behavior.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this surface does

System Settings / Detail is the dynamic editor for Core system settings. The page fetches the current settings plus the setting definitions, groups fields by group, and renders each setting according to its declared type.

Use it when you need to configure runtime behavior without redeploying code.

How the form works

  • Text, number, and boolean-like values render as normal fields.
  • JSON and HTML settings render in the code editor.
  • Encrypted settings render as password fields with a visibility toggle.
  • Update submits the form to Core and Core upserts each setting by definition name.
  • After save, Core refreshes the shared settings snapshots so downstream services can pick up the new values.

CRM Docs settings

  • CRM Docs Enabled: when false, the Backoffice help entry stays disabled even if a URL exists.
  • CRM Docs Base URL: the HTTPS origin for the docs runtime. If Backoffice is served over HTTPS, this must also be HTTPS or the browser blocks embedded/API access as mixed content.
  • CRM Docs Reviewer Emails: comma/newline/semicolon-separated allow-list for reviewer/editor access.
  • CRM Docs Lookup Timeout Ms: timeout used by the help drawer/API lookup path.

If CRM Docs is off or incomplete, normal CRM work should continue. Operators may lose inline help, but the product flow itself should not depend on docs being online.

Identity Graph settings

These settings configure Identity Graph integration for CRM/admin/casino-side graph sync and the restricted Identity Graph Control page.

  • Identity Graph URL, Identity Graph API Key, and Identity Graph Merchant Code are the base readiness fields.
  • Identity Graph Merchant ID enables customer projection readiness.
  • Identity Graph Merchant Name is display metadata for control/status screens.
  • Identity Graph Tags to Sync is the allowed tag list. Empty means tag sync is intentionally not ready.
  • Identity Graph Tag Match Signals controls tag dispatch matching. Supported values are email, phone, global_id, payment, and payout; empty/invalid values fall back to email.
  • Identity Graph Payment Evidence Sync Enabled lets eligible payment evidence be sent only when the base integration is ready.
  • Identity Graph SuspiciousPattern Enabled is the master capability toggle. Its default is on. Turning it off makes the SuspiciousPattern readiness capability inactive.
  • Identity Graph SuspiciousPattern Card Honeypot Enabled controls whether an eligible cross-brand card-deposit decision may be stopped before payment-provider dispatch. Its default is on; it does not apply to non-card methods.
  • Identity Graph SuspiciousPattern Failed Card Threshold sets how many failed card deposits without a later successful card deposit are required for source-brand activation. The default is 2; consuming services constrain the effective value to 1..20.
  • Identity Graph SuspiciousPattern Same-Day Cross-Brand Enabled limits the cross-brand honeypot policy to the configured same-day reference. Its default is on.
  • Identity Graph SuspiciousPattern Match Signals accepts email, uid, and ip. The default is email,uid; ip is evidence-only and must not trigger an automatic honeypot by itself.
  • Identity Graph HTTP Timeout in Milliseconds bounds outbound Identity Graph calls.

Turning off or clearing these fields disables the related sync capability instead of silently falling back to shared environment variables.

Same-day reference is visible on the dedicated Identity Graph Control page, with Registration date and First seen date choices, but its setting is not currently registered in Core. It therefore does not appear in this generic System Settings editor. The dedicated control page still submits it, so that page's complete save currently fails and rolls back until the product contract is aligned.

SuspiciousPattern settings affect fraud evidence and card-deposit handling across brands. Change them only with the fraud/payment owner, then verify the effective policy and a safe test flow before relying on the result.

Marketing Events settings

These settings affect downstream marketing/event delivery.

  • Marketing Events NOT sent to third-party: JSON allow/deny control for events excluded from third-party delivery.
  • Sent Manual Deposit/Withdrawal to Affiliates: controls whether manual wallet deposit/withdrawal adjustments dispatch affiliate third-party events.
  • Sent Only Depositors to CustomerIO: when on, CustomerIO sync skips users without deposits.
  • Sent To CustomerIO Who Register Days Ago: minimum age window used by CustomerIO selection.
  • Sent To CustomerIO Who Have Tags: comma-separated tag filter for CustomerIO targeting.
  • Sent all events to Third Party: JSON list of third-party event targets.
  • Third Party API Key: API key used by external third-party API checks.

Common confusion

  • Encrypted fields can be toggled visible in the browser, but stored values remain encrypted in Core.
  • Saving an empty encrypted field can overwrite a setting if the generic system editor submits it. For specialized pages like Identity Graph Control, use the dedicated control page when it has safer write-only behavior.
  • CRM Docs Reviewer Emails is not the same thing as the docs admin key. Emails decide who may request reviewer/editor access; the key is the server-to-server exchange credential.
  • The SuspiciousPattern match-signal list is separate from Identity Graph Tag Match Signals. The former controls fraud/honeypot matching; the latter controls ordinary tag dispatch.
  • A disabled or unavailable SuspiciousPattern capability is not proof that a player is safe. It means this specific automated policy is not active or not ready.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Actions3 topicsOpen details

Update

Action Type
submit
Preconditions
Current admin can open the System Settings page., Field names must exist in Core system setting definitions.
Side Effects
Upserts each setting by definition key/name/group., Applies each definition parser before storing., Encrypts settings whose definition has encrypt=true., Refreshes system settings and attempts to refresh shared casino settings cache.
Success State
The page shows "System settings updated" and rehydrates from Core settings.
Failure State
The page shows "Failed to update system settings" or the Core validation error; an unknown setting name rolls back the complete submitted transaction.

Toggle password visibility

Action Type
local-ui
Preconditions
The setting definition has encrypt=true.
Side Effects
Changes only local browser display type between password and text., Does not save or decrypt anything server-side.
Success State
The selected encrypted input is visible or masked in the form.
Failure State
No backend failure state; this is local UI state.

Edit JSON/HTML setting

Action Type
local-edit
Preconditions
The setting definition type is json or html.
Side Effects
Updates local form state until Update is pressed., Invalid JSON can be rejected when Core parser handles the submitted value.
Success State
The edited JSON/HTML value is staged in the form.
Failure State
Save can fail if the submitted value does not match the setting parser.
Calculations7 topicsOpen details

CRM Docs runtime enablement

Explains when Backoffice help can load docs.

Formula
internalDocs.enabled is true only when crmDocsEnabled parses true and crmDocsBaseUrl is a valid HTTP/HTTPS URL; lookup timeout falls back to 2500 ms when invalid or below 500 ms.

CRM Docs reviewer/editor access

Separates normal help lookup from elevated reviewer/editor access.

Identity Graph readiness

Determines which Identity Graph capabilities can run.

Formula
Base readiness requires URL, API key, and merchant code; customer projection also requires merchant id; tag sync also requires non-empty tags; payment evidence also requires its toggle; SuspiciousPattern also requires its master toggle, which defaults to true when unset.

SuspiciousPattern effective policy

Normalizes the fraud/honeypot settings before they are shown by the control page or consumed by the casino payment flow.

Formula
Enabled, honeypot, and same-day switches default to true; threshold defaults to 2 and is constrained to 1..20; match signals keep email, uid, or ip, map identity/device aliases to uid and ip_address to ip, remove duplicates, and otherwise default to email,uid. IP is evidence-only.

Dedicated control save contract

Explains why the dedicated Identity Graph Control form currently cannot persist its complete payload.

Formula
The dedicated page always submits Same-Day Reference, but Core has no definition for that name. Core rejects the unknown name and rolls back every setting in the submitted transaction. The generic System Settings page does not render or submit that missing field.

CustomerIO marketing eligibility

Shows why a user may be skipped from CustomerIO marketing sync.

Third-party marketing event dispatch

Controls whether and where marketing/event payloads are sent outside the platform.

Formula
Excluded events are filtered before third-party dispatch; manual deposit/withdrawal affiliate events depend on sentManualDepositWithdrawalToThirdParty; third-party API requests validate against thirdPartyAPIKeyForAPI.
More help

Related pages

System Settings

Grouped system settings editor for brand/runtime configuration, including CRM Docs, Identity Graph, and marketing-event integration settings.

Affiliate Payment Settings / Detail

Detail/edit shell for one saved affiliate payment-setting record.

Affiliate Payment Settings / Form

Create and edit form for one affiliate payment-setting record, with visible PID targeting, minimum deposit threshold, and active-state control.

Affiliate Payment Settings / List

Affiliate payment settings inventory page for reviewing configured rows and opening saved records.

Affiliate Payment Settings / Sending Window

Sending-window configuration tab for affiliate payment settings.

Affiliate Settings

Operator documentation for affiliate inventory, one-affiliate detail, and related conversion or PID performance reporting surfaces.