Skip to main content

Settings

The Settings group configures the workspace itself — branding, runtime tunables, gateway fleet and instance metadata. Every item requires org_admin or above; the group is hidden for lower roles.

Branding​

/settings/branding ("Org Branding") defines the identity that is embedded into every agent's system prompt, document and artifact — change it once and it applies everywhere.

  • Fields cover organisation name, tagline, light/dark logo URLs, primary/secondary/accent colours, font family, email signature HTML, footer text, contact details (email, phone, website, LinkedIn, address) and voice guidelines.
  • A single Save button persists the whole draft.

Config​

/settings/config ("Config") exposes tenant-editable runtime tunables. Saving takes effect on the next agent call — no redeploy.

  • Each setting is a card showing its label, help text, config key, default value and unit, with a numeric input (bounded by min/max where defined) and a per-setting Save button.
  • Sandbox-specific resource limits (memory, CPU, network) currently live on the Skills page under Resource Limits.

Gateways​

/gateways manages the gateway fleet that agents execute through.

  • Provision Gateway registers a new gateway by name.
  • Fleet Update pushes an update across the fleet and reports the result.
  • Gateways can be filtered by namespace, and each gateway has a config editor dialog for its individual configuration.

Config Templates​

/config-templates manages reusable configuration layers.

  • Create Template defines an org- or team-scoped template; the list can be filtered by scope, and templates are edited or deleted from their rows.
  • A Config Resolution tester picks a gateway and shows its effective configuration along with every contributing layer, in resolution order: org defaults, then team policy, then gateway config.

Admin Console​

/admin is the at-a-glance administrative dashboard, with Overview, Users and Billing tabs.

  • Overview shows:
    • Fleet health — gateways online, agents active, active sessions.
    • Activity (7 days) — sessions, audit events, approval requests, tokens consumed, tool calls.
    • Security alerts (24 h) — failed logins, denied approvals, error sessions, each with a threshold indicator.
    • Compliance posture — MFA and SSO coverage bars, retention policy and permission rule counts.
    • Policy overview and token consumption by agent (30 days).
  • Users summarises user management: totals, active/inactive split, role distribution, recent activity, and SCIM configuration/sync status.
  • Billing summarises plan and consumption for the tenant.

General​

/settings ("Settings") carries instance-level and account-level settings in sections:

  • Organisation — organisation name, plan and deployment mode.
  • Security — authentication method, JWT token expiry, a Copy JWT helper for testing API endpoints (treat it as a password), the active SSO providers summary, and MFA setup or disable for your own account.
  • Integrations and Infrastructure — read-outs of connected surfaces and infrastructure endpoints.
  • Environment — deployment metadata such as mode and version, available even on an empty instance before any tenant exists.
  • Personal API Token — issue a token for scripting against the API as yourself.

A Save Changes button appears whenever there are unsaved edits.

Platform operators also see a SaaS Operator sidebar group (Tenants, LLM Pool) below Settings. It manages the hosted control plane — tenant lifecycle and the pooled LLM credentials — and is documented in the operator guide, which ships as a separate documentation set.