Skip to content

Settings

Tenant-scoped configuration. Five sub-pages share a tab navigation.

Base route: /settings Role gating: read for all; write varies per sub-page.

Account

Route: /settings Role gating: authenticated user (self-service).

User account settings:

  • Change password.
  • Notification preferences.
  • API token management.

LLM

Route: /settings/llm Role gating: admin.

Per-tenant LLM provider configuration.

Providers

openai, deepseek, anthropic, kimi, llamacpp, vllm.

Per-provider fields

  • API key (stored encrypted).
  • Base URL override (optional).
  • Default model.
  • Temperature.
  • Max tokens.

Actions

  • Edit dialog per provider.
  • Test Connection — pings the provider and reports the result inline.
  • Refresh Models — pulls the live model list from the provider for use in the Agents detail dropdown.

Prompts

Route: /settings/prompts Role gating: admin.

Manage Jinja prompt templates used by the agent pipeline. The platform ships defaults under templates/prompts/*.jinja2; per-tenant overrides live in the database and take precedence when present.

Editable templates

  • stage_triage
  • stage_diagnose
  • stage_validate
  • stage_execute
  • stage_review
  • evidence_summary
  • Custom-incident branches of the above.

The editor accepts standard Jinja syntax. Available variables are documented inline.

Servers

Route: /settings/servers Role gating: admin.

Global server-monitoring defaults applied to new servers in this tenant:

  • Discovery settings.
  • Default alert policies.
  • SSH timeout.
  • Daemon polling interval.

Guardian

Route: /settings (Account tab, Guardian section) Role gating: read for all; write requires admin.

Controls how OpenRemedy behaves when the Guardian safeguard is unreachable.

Setting Meaning
Fail open (default) Treat Guardian's result as absent. Risk levels are unchanged and the standard approval gate decides as normal.
Fail closed Force risk to high on every Guardian failure, requiring human approval regardless of the recipe's declared risk or agent trust level.

Changing this setting writes a tenant.guardian_fail_mode.updated audit row.

Users

Route: /settings/users Role gating: admin.

Tenant-scoped user management. (Cross-tenant management lives under admin.md.)

Columns

  • Email.
  • Role (user / admin / superadmin).
  • Status (active / inactive).
  • Edit / Delete buttons.

Actions

  • Add user. Modal: email, password, role.
  • Edit role.
  • Deactivate.
  • Delete.
  • agents.md — agents reference the LLM providers configured here
  • audit.md — every state-changing action recorded here is audited