Skip to content
Optima docs
ConsoleSettings

Instance settings

Review and change the instance-wide settings that apply to every environment, without a restart.

Instance settings are the platform-wide switches and limits that apply to every environment on your Optima instance, such as privacy defaults, size limits, lifetimes, identity behaviour and the defaults for AI assists. A change is saved from the console and takes effect on its own within seconds, with no restart. Open it under Settings → Instance → Instance settings.

Who uses it

Only instance administrators, the people who run the whole instance. The instance_admin role is required; everyone else does not see the entry, and opening the address directly shows "Instance settings are restricted to instance administrators". If you run your own environment on a shared instance, your platform operator manages these settings for you, and your own switches live on screens such as Privacy and Notifications.

Fields

A search box (Search settings by name or description) filters across all groups. Without a search, tabs split the settings into groups.

GroupWhat its settings cover
Privacy & consentPlatform-wide privacy behaviour and consent defaults
LimitsSize and rate limits
LifetimesHow long things stay valid, for example how long a rotated API key's predecessor keeps working
IdentityDefaults for identity resolution
EdgeBehaviour of the public tracking and content gateway
NotificationsDefaults for notification delivery
AI assistsDefaults for AI features
CampaignCampaign delivery behaviour
ConnectData connector behaviour
RecommendationsRecommendation defaults

Each setting shows its name, a description, and a control suited to its kind: a switch (Enabled or Disabled), a choice, a number (with its range), text, or a secret. Badges tell where the current value comes from: Instance when someone set it here, Environment when it is the default from the deployment. A Governance badge marks settings that strengthen or weaken a privacy control; changes to them are logged with who made them. A line below says what the setting falls back to.

Secret settings are write-only. A stored value shows "A value is stored. Type a new one to replace it, or reset to fall back to the environment." If the instance has no encryption key configured, secrets stay at their deployment value and cannot be edited here.

Actions

  • Change a value; the setting is marked Edited and the bar at the bottom shows "N unsaved changes".
  • Save applies every edited setting together. Validation is all or nothing, and your edits stay in place if something is refused.
  • Discard all drops every unsaved edit, and Undo next to a setting drops just that one.
  • The reset arrow on a setting that was set here returns it to the deployment default; it is marked Will reset until you save.
  • After saving, the change is in force across the whole instance within the interval the screen states.

If a setting sends data somewhere new, the screen may ask you to enter the related secret again before it saves.

Examples

Find a setting. Type a word from what you want to change, for example session, in the search box. Matches from every group are listed together.

Roll back a change. Use the reset arrow on the setting, then Save. The setting returns to the deployment default.

Common problems

  • "Instance settings are restricted to instance administrators." Your account lacks instance_admin.
  • A secret cannot be edited. The instance has no encryption key configured. Ask your platform operator.
  • A save is refused. A value is out of its range or a secret is missing; fix it and save again, since nothing was applied.
  • A change does not seem to apply. Wait for the propagation interval shown on the screen.

On this page