# Using the WebUI — settings and administration

**A screen not listed here does not exist.** Headings quote the screen's own wording.

**The other files:**
conversations, the input box, and sign-in: `references/webui.md`;
documents, files, tables, memory, skills, channels, and apps: `references/webui-workspace.md`;
editing files: `references/webui-file-edit.md`;
SIROE pages, blocks, and boards: `references/webui-siroe.md`;
external service connections: `references/webui-connections.md`;
`/office`: `references/webui-office.md`;
`/meetings`: `references/webui-meetings.md`;
`/calendar`: `references/webui-calendar.md`.
「管理」 (workspace, members and groups, permissions, usage, subscription, compliance and the audit log) is in `references/webui-settings-admin.md`.
「個人設定」 (your own account, email address change, signed-in devices, color scheme, issue reports, `/features`) is in `references/webui-settings-account.md`.

**Each section of the settings screens has its own URL** — the link icon right of a heading appends `#section`; opening that URL scrolls there.

## 「エージェント」

| Where | What it configures |
| --- | --- |
| `/settings/triggers` | 「自動実行」 (formerly 「トリガー」). Runs an agent unattended, **4 tabs** — 「定期実行」 (fixed times in Japan time, at most hourly. **An end date can be set; it runs on that day and stops from the next day**), 「外部から起動」 (issues one URL-and-secret pair, called from Slack, Zapier; secret in the `Authorization: Bearer` header — `?k=` in the URL only with 「URL の ?k= でもシークレットを受ける」 on, off by default), 「サービス連携」 (runs on events from connected Gmail, GitHub, etc.; no URL pasting needed. **Costs about 0.5 yen per event received, even when nothing runs**), and 「アプリ内の出来事」 (on in-app events: 「ミーティングの議事録が確定した」; it does not fire for a meeting the trigger's owner or 公開範囲 cannot see. **The add form always runs an agent; above it, 「議事録を通知先へ送る」 registers a no-AI notice to a 通知先 instead** (no credit cost). See `references/webui-meetings-records.md` for minutes). **Only admins and managers can create 外部から起動する registrations and サービス連携.** **Outcome reports are chosen per registration**, for email and webhook each: 「送らない / 失敗したときだけ / 成功したときも」. The default is 「失敗したときだけ」 for email and 「送らない」 for webhook. Email goes to oneself; webhook to a `/settings/notifications` destination. Actions (「今すぐ実行」「編集」「削除」) are in the row's 「…」 and atop `/settings/triggers/<id>`, which has run history, run conversations and a folded 「設定」. **Each registration has a 「公開範囲」** — 「自分のみ」 (the default for new ones) / 「グループ」 (groups the user belongs to) / 「テナント全体」. Others in the scope get 「閲覧のみ」 (read settings and runs; actions disabled with the reason). **Only the creator and admins/managers can change it**. Non-creators (admins/managers too) read run conversations read-only; nobody reads runs outside their scope. **With scope 「グループ」/「テナント全体」 and the creator's own skill, 「スキルも同じ範囲に共有する」 appears, checked by default** — saving shares a copy of the skill there. Narrowing the scope later does not remove the shared copy. **All types are read together at `/settings/triggers/overview`** — counts, failures, success rate, and time-of-day over 24h / 7d / 30d windows (mine / everyone). **A registration can run as a bot** (「ボット」; made in a bot's chat, it takes that bot). Deleted/off bot: runs fail, row shows 「ボットが見つかりません」. 「使うスキル」 lists only the bot's. **Registrations added from a workflow's 「トリガー」 tab are listed here too**: the row shows the workflow's name (click it to open the workflow; 「ワークフローが見つかりません」 once it is deleted), and 「設定」 shows 「動かすワークフロー」 in place of the prompt and skill, noting when the workflow is not published yet. **Trigger conversations do not appear in the sidebar.** 「この自動実行が使う操作」 lists what passes approval without a card in an unattended run. **Any other operation needing approval raises an approval card for the trigger's owner (push notification and 「受信トレイ」) and waits up to 20 minutes; unanswered, the run fails.** Operations that went unapproved show on the detail page to allow |
| `/settings/notifications` | 「通知」. **2 sections.** **「ブラウザ通知」 is notifications delivered to your own device** — they arrive even with the page closed, with 6 switches (3rd 「運営からのお知らせ」, 4th 「SIROE のコメント」, 5th 「コンプライアンス」, for admins and managers when the patrol finds something, 6th 「予定のリマインド」, **5 minutes before each timed calendar event you have not declined** — `「<title>」が 5 分後に始まります`, recurring occurrences included, never all-day events; the lead time is fixed) — **the same 3 switches also sit as a 「通知」 menu at the top of 「お知らせ」, SIROE, and the compliance findings**: 「ターンの結果」 (completion of responses that took 30s+, showing the reply's start, plus failures, interruptions, waiting for approval, waiting for confirmation, a question to your own clone bot whose draft answer is ready to review, and **whether each run of a scheduled or externally triggered job you created succeeded or failed** — `「<name>」のジョブが成功しました` / `…失敗しました`, every run, even with email notifications off; **the end of a workflow run you started** — `「<name>」のワークフローが成功しました` / `…失敗しました`, not for public-form runs or step tests; and, for meetings you created, **when the minutes are saved** — `「<title>」の議事録ができました` — and **when the meeting analysis is ready** — `「<title>」の会議の分析ができました`; and **while you are in a call, when an outside guest asks to be let in from the waiting room** — `「<title>」で<name>さんが入室をリクエストしています`, only to the device you are calling from and only while the call tab is not in front; clicking it brings the call back to admit or deny) and 「チャンネルの発言」 (**this switch is the parent**: which messages ring is chosen per channel from its 「⋯」; by default only mentions). **The setting is per device** (the screen lists your devices; any can be removed, and each row's 「テスト送信」 sends that device one test notification even with every switch off). **On iPhone/iPad (iOS 16.4 or later) it only works after adding the app with 「ホーム画面に追加」 from the share menu of Safari or Chrome and opening it from the home-screen icon** — while it is open in a browser tab, the 「ブラウザ通知」 section shows these 4 steps instead of the switches, and the 「通知: オフ」 menu atop chat, SIROE, compliance, and 「お知らせ」 shows a short version with 「追加の手順を見る」 linking here. On iOS 26 Safari the share button sits under 「…」 and 「ホーム画面に追加」 under 「その他」. **The home-screen app has no reload button: pull down from the top** (unsaved edits ask first). Unsupported browsers and older iOS show 「この環境ではブラウザ通知を使えません」. **「通知先」 is the registry of destinations (e.g. Slack) that trigger outcomes are delivered to** (shared across the tenant). Register by entering a name and a webhook URL; **a registered URL is never shown again**. **A row's 「編集」 renames it or takes a new URL** (empty keeps it); triggers keep sending to it. 「テスト送信」 sends one test message. **Only admins and managers can register, edit, and delete**. Deleting one stops the trigger webhooks sent to it |
| `/settings/models` | Models in use and bring-your-own keys |
| `/settings/agent-soul` | 「性格」. **「見た目」 at the top picks the main agent's face (one of 36 avatars) for everyone** — shown beside its replies and in the office. Only admins and managers change it. Below it, one field describes how requests are handled. **4 templates: 「標準」「自走」「簡潔」「辛口」.** Choosing one fills the field, **then edit it freely** (up to 2000 characters; may be empty). 「標準」 confirms unclear points first; 「自走」 checks what it can by itself and states its assumptions in the reply. 「簡潔」 leads with the conclusion, short; 「辛口」 opposes weak proposals with reasons — these 2 keep the 「標準」 stance, changing only the style. **It can apply at 3 levels: 「自分だけ / グループ / ワークスペース全員」**; the narrowest one set wins. **Anyone can write their own**; group and workspace levels are for admins and managers. **Tool usage and descriptions, the date/time, the discipline of not reporting things not done, proposing approvals, and asking about turning work into skills are always passed** (性格 cannot remove them). **It applies from the next turn** (unlike memory, not frozen per conversation). **Channels, 定期実行, and runs from 外部チャット use the workspace's 性格** — several people read them, so no one person's is chosen. **性格 does not apply to business agents (delegation targets).** |
| `/settings/completion` | Input completion |
| `/settings/knowledge` | 「ナレッジ設定」. **Search language settings** and **label vocabulary** (**create and delete** names. **Anyone** can create; **only admins and managers can delete** — deleting removes it from every file in the tenant). **Members can open this surface too** (creating vocabulary has no role restriction); unavailable sections are not hidden but show the reason. **The list of uploaded files and the ways to add more (local files, importing from a site) are under 「ナレッジ」 inside 「ファイル」** |

### Models used (LLM)

`/settings/models` is **閲覧のみ (view-only)**. The tier is picked per message in the input box (「モデル」).

- 「**いま使われている既定**」 shows 2 entries: the main conversation flow and conversation compaction.
  On a bring-your-own key, the key in use is shown too.
  When the registered key has no usable model for some tier (for example 「最上位」 for the main flow),
  a note 「標準の鍵で動く組み合わせ」 lists those combinations: they run on the standard key (OpenRouter), and the conversation is sent there
- 「選べるモデル」 is listed by tier: **fast (mechanical steps) / standard (main flow) / frontier (top tier)**.
  Prices are per 1M tokens, as of the list's build.
  **Check the screen for which models are listed** — the lineup changes
- **A model name (the 2 default rows and every list row) opens its OpenRouter detail page in a new tab** — check current prices and context there. **Only when running on an operational pin (environment-variable override)
  is the default row not a link** (that name has no detail page)
- 「**判断専用モデル**」 lists the decision-only model, which is **never chosen by tier** and never writes a reply.
  It is called from a script's `decision.choose` / `decision.rate`, the conversation's `judge`, and background checks
  such as document screening and approvals. Its name is not a link; cost is shown per call, not per token
- 「**モデル接続**」 lets you bring your own key. The providers are 6: OpenRouter / OpenAI / Gemini /
  OpenAI-compatible endpoint / Azure OpenAI / Amazon Bedrock. Scope is 「個人」 or
  「テナント共有」; admins and managers can create テナント共有 ones, and so can a member while no テナント共有 connection is active (the member who created it may disable or delete it). **The last 3, where you write the destination yourself
  (OpenAI-compatible, Azure OpenAI, Bedrock), can also only be created by admins and managers**, and the destination is limited to
  hosts not blocked in `/settings/permissions` (「許可設定」) (no registration needed).
  **「編集」 changes the label, key (empty keeps it), or own-destination model names; a new key is test-called, then re-enables it** (provider, scope, destination are fixed). **A deleted key can never be used again**
- **Reasoning strength (思考時間) is not changed here.** The default model's shown strength applies when nobody chose one (scheduled runs etc.);
  change it per message in the input box (default 「自動」, remembered per conversation)

## 「認証」

| Where | What it configures |
| --- | --- |
| `/settings/connections` | 「コネクタ」. External service connections (connectors, API connections, use from external AI). **Details are in `references/webui-connections.md`** — how to connect, company-wide shared accounts, and what each SaaS can do from chat are there. 「**SmartDB**」 on the same tab is connected by admins and managers with a binder token; **there is no per-user identity check — it acts as the token's robot user** (only the registered binders are reachable) |
| `/settings/secrets` | Keys for external services. **There is no way to read them back** (only to enter and pass them). Scope has 3 levels — 自分のみ / グループ / テナント全体 — and **for the same name, 自分のみ > グループ > テナント全体 wins in that order** |
| `/settings/browser-logins` | Login state used by browser operation. **After finishing a login in Live View**, the domains passed through along the way are offered as 「共通ログイン」 candidates — **none are selected by default**, and only non-blocked domains can be chosen. Once selected and saved, that domain's cookies are **injected into the browser first whenever any site is opened**. **The scope is the same as that site's registration**, and the candidate section shows something like 「公開範囲はテナント全体(このサイトと同じ)」 — selecting on a tenant-wide registration injects into everyone's browser. The 「サイトを追加」 form first asks 「保存するもの」 as two cards — 「ID とパスワード」 (**selected by default**; needs 「ログイン画面の URL」 — **there is no 「ドメイン」 field: the registration's domain is the login URL's domain**, so a site whose login page is on another domain, such as `auth.example.com`, is registered with that login page's URL) and 「ログイン済みの cookie」 (enter the 「ドメイン」; log in afterwards with 「ログインして保存」, or paste cookies). The cookie-login registration form has a 「共通で使う」 checkbox, and shared-login rows in the list carry a 「共通」 badge. **Multiple accounts can be registered for the same site** — the list is grouped by host, and any number of registrations with different names can sit under the same host and scope (the name is 「ログインの名前」 in the registration form; duplicates are not allowed within the same host and scope). **The row's radio button is 「既定」**, used when a conversation or script does not specify a name — for a host with several rows and no default, operations that do not specify a name are **refused**. To choose from a conversation, pass the name to `browse`'s `navigate` (passing a different name logs out of the previous login before opening). Each row shows one next-step button — 「ログインして保存」 (cookie) or 「入力」 (ID and password), outlined while the row is 「未設定」 — and folds the rest (「貼り付け」 for cookie rows, 「編集」, 「複製」, 「失効」) into its 「…」 menu. **Registering an ID-and-password login opens the ID/password input right away.** A row's 「編集」 fixes the login URL (**within the same domain** — a login URL on another domain is refused with 「ログイン URL には <domain> のページを入れてください」), logout URL, or **「公開範囲」** without revoking — saved values move with it. Refused if the destination scope has the same name; only managers or above, or the row's creator, can widen it to テナント全体 (**the name, domain, and 保存するもの cannot be changed by editing** — scripts that wrote that name would be refused). A row's 「複製」 pre-fills a new form (**named 「<name>のコピー」; ID, password, and cookies are not copied** — enter them with 「入力」). **Only ID-and-password registrations have 「ログアウト URL(任意)」** — if set, switching to another login visits it once to close the session on the other side. Cookie registrations do not have it (logging out kills the saved cookies, so only registrations that can log in again every time can have one). **It can also be saved without opening this screen, via 「ログインを保存」 that appears after logging in by hand in chat** (Live View, or a `samuraiapp tunnel` browser). It lists here as a private login, never overwriting company-wide or group-shared accounts. Once saved, the card says 「次からは、このサイトを開くよう頼むだけで、ログイン済みで開きます」 — **from then on, just ask the AI in any chat to open the site**; there is no need to log in again. Its optional 「ログインの名前(任意)」 defaults to the domain; a name already used replaces that login. Its 「ID とパスワードで保存」 saves the ID and password instead (one or the other) — for sites whose cookies expire quickly. Its 「ログイン画面の URL」 is pre-filled with the page where the password was typed, and **the row is registered under that login page's domain** (shown as 「<domain> のログインとして登録します」) — for a site that sends you to `auth.example.com` to log in, that is `auth.example.com`, not the site you opened. **For an SSO login where the password is typed on one domain and the browser lands on another** (Google's `accounts.google.com` → `myaccount.google.com`, Microsoft's `login.microsoftonline.com` → Microsoft 365), the card appears for the domain landed on, and the domain where the password was typed is **pre-selected** as a 「共通ログイン」 candidate so other services of the same IdP open signed in too — unchecking it saves only the landed domain |
| `/settings/cli` | 「PC と繋ぐ」. **The 「インストール」 tab opens with a 5-step guide** — open the terminal (Terminal / PowerShell, with the keys) → install → sign in → register this machine (the standard-settings `tunnel register` line) → connect (`tunnel serve` / `tunnel install`). Only the current step is open; 「できた」 moves on, and register and connect also advance by themselves once the device appears in the list (「最初から」 resets). Composing the connect command in detail (**`tunnel register` with the standard settings is on the 「使う」 tab** — a single line allowing read/write of `~/Downloads`, script execution, and browser operation (including typing and clicking); changing the allowed folders and capabilities rewrites it on the spot. **The settings are split by permission into 5 steps** — 「どのフォルダを許すか」 (presets, a typed path, and 「端末でフォルダを選ぶ」: turning it on adds `--pick-folder`, so running the command opens the OS folder dialog on that machine and adds the chosen paths), 「フォルダの中でさせること」 (「読むだけ」「読み書き」「スクリプトも実行」, plus 「フォルダの中のファイルの削除も許す」), 「ブラウザ」 (a switch, on by default; 「見るだけ」 or 「入力や押下も」; which browser — 「専用の Chrome」「専用の Edge」「普段使いの Chrome」 — with the profile name or the CDP address for the chosen one; for a dedicated browser, 「ウィンドウを出さずに動かす」 adds `--headless`, and recording still opens a window), 「PC のアプリ」 (a switch, off by default, macOS / Windows only — adds `--desktop write` (「見るだけ」: `read`) and shows the cua-driver setup for the OS), and 「手元の Claude Code」 (a switch, off by default — adds `--agent claude-code` and shows how to install and sign in to Claude Code; see the CLI reference for its limits). Only 「そのほかの設定」 (device name, per-file limit, expiry) is folded. Removing all folders (with 「端末でフォルダを選ぶ」 off) hides it. **The 2 commands to run next — 「いま 1 度だけ繋ぐ」 (`tunnel serve`; connected only while that window stays open, Ctrl-C stops it) and 「ログインしたら自動で繋ぐ」 (`tunnel install`; connects at every login, stopped with `tunnel uninstall`) — are shown regardless of input.** Registering alone does not connect; recording does not need it). **「自分の作業を録って手順にする」 opens with what each stage needs** — 録る: the browser grant, 会話にする: sign-in, neither needs the device connected; only 「できた手順を動かす」 needs `serve` / `install`, plus the list of registered devices and revocation (each row names what it allows in the builder's words — folder 読むだけ / 読み書き・削除, scripts, browser, app control, and 手元の Claude Code). **Expiry defaults to 30 days, maximum 365 days, and is extended each time it connects**. **Registration itself happens only on the device** — the screen only makes a string to paste. **The surface is split into 3 tabs — 「インストール」「使う」「登録した端末」** (`?tab=install` / `use` / `devices`), and **the OS (macOS / Linux / Windows) is chosen at the very top of the surface** — it can be changed from any tab, and the install steps, the quoted connect command, and the removal steps all change together. **How to stop using it is on the 「登録した端末」 tab** — opening 「使うのをやめる」 lists 4 steps with commands: stop auto-start → revoke → sign out → delete the binary and settings (the order matters; `logout` does not stop the resident process). **「フラグを覚えずに画面で操作する」 shows `samuraiapp` with no arguments** — running it opens an interactive screen in the terminal for sign-in, registering and connecting this machine, and recording work (**no flags needed**: arrow keys and Enter, typing only the MCP URL, folder paths, and machine name; close with 「終了」 in the menu. From a script or CI it shows the command list instead). **「手元のエージェントへ使い方を渡す」 downloads the usage of `samuraiapp` as a skill** — extract `samuraiapp-cli.zip` and place it under `~/.claude/skills/`, and a local Claude Code or similar knows how to call it (the host and tenant ID at download time are embedded) |
| `/settings/chat-surfaces` | 「外部チャット」. Registering a Slack workspace, or a Microsoft Teams / LINE / Chatwork bot, or a Facebook page (Messenger), lets people call the agent from **any channel, group, or room the app or bot has been added to** — no channel or room ID is entered; the form asks only for the platform, the two secrets, and an optional display name, and the workspace or bot is read from the token. **One Slack workspace can be registered by only one tenant.** For Chatwork, the webhook must be the account event for mentions to the bot. **The add form's 「つなぐ手順」 lists, for whichever platform is chosen (Slack, Microsoft Teams, LINE, Chatwork, Messenger), a link to that service's console, what to do before and after adding, and the settings that break silently.** **Only admins and managers can create and delete them**; anyone can pause, resume, or switch the calling mode. **Anyone can also rename a channel with 「編集」 in the row's 「その他の操作」 menu** — on a LINE channel the same dialog changes the text people use to call the agent. The platform, the workspace or bot, and the secrets cannot be changed; to change them, add the channel again. **The default is 「呼ばれたときだけ返答する」.** **Nothing runs as anyone until the person calling has completed linking** — the first time, a linking notice visible only to that person is returned in the chat (in Slack it carries a 「Samurai App と紐付ける」 button; elsewhere a link to `/chat-link`, valid for 1 hour); open it while signed in to Samurai App and press 「紐付けを確定する」. **The request that triggered the notice then continues as is** — no need to mention the bot again; the reply arrives in the original thread. **In Slack, with 「Agents」 enabled in the Slack app (listed in this screen's setup steps), the thread shows a working status and the reply is written out as it goes, with each step (search, reading files, etc.) shown as a task in it**; without it, the reply arrives as one message after it finishes. Replies grounded in files under personal permissions still go only to the requester, and their text is never streamed. Teams, LINE, and Chatwork always reply in one message after finishing. Both tokens are **picked from tenant-shared secrets** in `/settings/secrets`. **Each call starts a conversation per thread, and answers are posted back there** (there is no narrowing; replies grounded in files under personal permissions can also appear). **Those conversations appear neither in the history nor in 「すべての会話」** — read them at `/settings/chat-surfaces/<連携先>`. **「統合チャットに入れる」 (row 「⋯」) and choosing which channels and rooms appear there**: `references/webui-workspace-channels.md`. **When a Samurai App URL (a siroe page, or a file's public URL) is pasted in Slack, a card with its title and opening lines appears only if the person who pasted it has completed linking and can read it** — the card is visible to everyone in the channel. This needs `link_shared` and 「App unfurl domains」 in the Slack app (listed in this screen's setup steps). Anywhere else (Notion, X, etc.) only public URLs of files and conversations (「外部公開」) (the file name, or the conversation's title — never its messages) and public apps (their title and description) show a title; every other URL shows a card with just 「Samurai App」 |
| `/settings/approvals` | Two tabs: **「承認者」** (the approver roster, the default) and **「依頼」** (approval requests and each approver's answer). **External people can be registered too** (members: 「メンバーから選ぶ」). **The deadline defaults to 72 hours, maximum 30 days**; **up to 5 approvers per request**, and the roster is for admins and managers only; if not everyone answers by the deadline, it is not approved and the conversation continues with that result. **Approvers receive an email titled 「【承認のお願い】」 and open its link (`/r/<token>`) without signing in** — pressing 「承認する」 or 「却下する」 sends a 6-digit confirmation code to the same address (valid 10 minutes), which they enter to confirm. **An approver whose email matches a member's verified account email shows a 「メンバー」 badge; that member also gets a browser notification and an entry in 「受信トレイ」, and can approve or reject inside the app at `/approvals/<id>` without a confirmation code** (the email link still works too). It passes when everyone approves; a single rejection makes it not approved |

## 「管理」

`/settings/workspace`, `/settings/members`, `/settings/permissions`, `/settings/usage`, `/settings/subscription`, and `/settings/compliance` are in `references/webui-settings-admin.md`.

## 「個人設定」

`/settings/account` (your own account: icon, names, email address, signed-in devices, announcements, the bottom-right buttons), the color scheme, issue reports, and `/features` are in `references/webui-settings-account.md`.