Manage preferences, custom metrics and notifications

Use the settings section that owns the change

Preferences, Metrics and Notifications are related account tools with different jobs. Preferences changes application display behavior and saved defaults. Metrics stores supported expressions. Notifications shows the recent account inbox and the effective email policy. Moving between these sections does not make their controls interchangeable: a notification preference cannot repair a metric expression, and changing the application theme does not subscribe an alert to email. Begin by naming the result you want, then open the section that actually owns it.

Set display and saved-resource preferences

Preferences includes reduced motion, optional implied SPX and NDX prices when matching closed-market inputs exist, appearance and supported default resources. Default workspace or watchlist references must belong to your account. Choose an existing saved resource rather than a name you remember from another account. An implied estimate is labeled separately from official prices and captured trades; enabling its display does not turn an estimate into an exchange observation. Save ordinary preference form changes through the relevant action and wait for confirmation where the control is not an autosaving appearance picker.

Explore custom metrics from the field catalog

Open Settings → Metrics and expand Available metric fields before writing an expression. The list describes the server-approved inputs. Enter a descriptive Name and Expression in New metric, then use Validate to inspect the returned result. Validation checks the supported calculation contract rather than granting arbitrary execution or access to unrelated data. A field that exists in a chart's visual legend is not automatically an expression identifier; use the actual field catalog. Keep the expression small enough to understand and verify before combining multiple calculations.

1. Inspect Available metric fields and choose the inputs you need.
2. Enter the expression and use Validate before saving.
3. Save metric and confirm the resulting record appears under Your metrics.

Interpret a saved expression carefully

A valid saved expression can still lack current inputs for a selected instrument or session. Missing observations do not become zero simply because a formula uses subtraction or a ratio. Review source coverage when comparing a custom calculation with a chart, and check units before interpreting the result. Delete an obsolete record from Your metrics when you no longer need it. Use a distinct, explanatory name for a separate calculation so an old name does not imply that the underlying expression changed everywhere automatically.

Read the recent notification inbox

Notifications is a bounded recent account inbox, not a permanent archive of every event. Entries stop appearing after seven days, and the recent view is also limited to its retained pointers. Marking an entry read changes its inbox state; it does not acknowledge a payment action or pause a saved alert. Alert firing history, invoice records and support conversations have separate views. If an old notice disappears from the inbox, consult the owning feature before concluding that its underlying record was deleted.

Understand the current email policy

The current effective policy sends essential billing, account-information and security notices immediately. Routine alert, activity, market, developer-project, export and operational events remain inbox-only; older immediate or digest preferences cannot enable email for them. Developer key security events can be eligible security notices. Customer-requested support replies are a separate explicit email workflow from noreply@ordermap.si. A displayed older preference or an earlier help description is not authority to expect routine alert mail. Read the current controls and event behavior rather than planning around a digest that is not offered.

Check the actual outcome of a settings change

After a save, verify the saved preference, metric record or read state in the feature that owns it. A successful profile-information change may create an essential account notice, while changing reduced motion or a default workspace does not create the same email. For delivery problems, distinguish queued, provider-accepted and delivered states from placement in your inbox. For metric failures, provide the expression, field names, selected instrument and safe validation error. Never include passwords, reset links, session cookies or full developer keys when reporting a settings problem.