Web UI

Create and edit records

Open a record's create or edit form from its list. Changes take effect only after the server accepts the form.

For: People using the web UI.

Open a record's create or edit form from its list. Changes take effect only after the server accepts the form.

Adding and changing records

Creation forms open from buttons beside their lists so the page stays focused on existing records:

PageAction
Access → API keysCreate key, Register app
Models → Aliases, Mapping rules, CanariesAdd alias, Add rule, Add canary
Settings → Notifications, Plugin settingsAdd notification rule, Add setting
Privacy → LabelsSet agent clearance, Add wall, Set person clearance, Set egress rule
Privacy → ErasureSet keep-for rule
Policy → RulesAdd duty, Add duty pair
Budgets → QuotasSet quota
Chat channels → PeopleLink account, Map person
Credentials → SecretsAdd Secret, Reminder settings
Cluster → Temporal backends, RegionsMove tenant, when another destination exists

Aliases and plugin settings also have Edit on each editable row. Cancel discards the dialog's draft; a rejected save keeps it for correction. While a request is pending, its fields, submit button and cancel action are disabled. A successful request closes the form and refreshes its list. Created API keys, app keys and chat link codes remain visible on the page until dismissed, so they can be copied.

Required reasons are collected with each governance action, including removal of label policies, duties, duty pairs and governed settings. Where four-eyes review applies, the result says that the change awaits another admin; it does not claim the change has already taken effect. The same permissions still decide who may open each form.

Focused editing

Lists show current records first. New tenant, New account, Add provider and Stop something open a dialog; unsaved edits are protected when closing. Provider editing identifies whether the record is shared or belongs to one tenant. Account creation displays its one-time result above the accounts table.

Privacy shows the current retention, legal hold and backend state before Edit retention and Place legal hold. Existing warnings and required reasons remain visible in the relevant form. Monthly budgets have a visible Save button; Enter still submits the field.

Tools show function and node counts, with approval changes and policy counts visible. Expand a count for the full function descriptions, policy verdicts or node names. Question-mark buttons open contextual help dialogs for search syntax and background explanations across Policy, Privacy, Models, Access, Credentials, Settings, budgets and comparisons. Open them by click or keyboard; Escape or Close returns you to the page. Required instructions, costs and warnings stay beside the controls.

Forms, appearance and updates

Schedules, durations and expiry fields offer presets and manual entry. Reference fields search the tenant's catalog and configuration. A single value stays editable in its selector; fields that accept multiple values accumulate chips with remove buttons inside the selector. You can also enter an unpublished reference. Suggestions contain names, never secret values, and the server still checks permissions and validity when you save.

New routines and structured Studio files open in Form. Editor or Definition remains available for the source. Studio keeps the selected file when its sidebar link is clicked again. Its form retains unapplied edits when switching views; apply or reset them before changing files. Tabs stay above list filters so switching tabs does not move the tab bar. When a tab under More is open, the More button names it and is the only highlighted selection.

The account menu at the bottom of the sidebar has Appearance → Light, Dark, and Use system setting. The preference stays in this browser. Cluster → Regions includes the default region when an edge has no configured region name.

Job details and chats use the existing authenticated streams. Management lists retain their rows during background refreshes; those reads pause in hidden browser tabs, stop when the page closes, and wait for the previous read. The approval count is shared across pages. Management-wide push events are not yet available, so these lists and the approval count still use bounded polling. The browser does not connect to NATS.

The Chats button in a page's top-right corner opens the tenant's agent conversations beside that page. It is the same set of accessible conversations as Chats in the sidebar: continue a conversation, see its job's progress and answers, or respond to a question or approval. The badge calls out unread or waiting activity. Use Ctrl J (⌘J on macOS) to toggle it.

On the full Chats page, New chat below the empty conversation pane opens the same agent picker as the header button, keeping your tenant and time filter. Compare keeps its tabs in the same position across Jobs, Versions, and Drafts and revisions, including on small screens.

Back to Web UI.

Copyright © 2026