Samurai AppDocs

Using the WebUI — channels (/channels)

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

Part of the workspace guide. Other topics: conversations, the input box, and sign-in: references/webui.md; documents, files, tables, memory, channels, and apps: references/webui-workspace.md; editing a file in place (「編集」): references/webui-file-edit.md; SIROE pages, blocks, and boards: references/webui-siroe.md; settings, administration, models, and triggers: references/webui-settings.md; external service connections: references/webui-connections.md; /office: references/webui-office.md; /meetings: references/webui-meetings.md; /calendar: references/webui-calendar.md.

「ワークスペース」 — channels

Where What you can do
/channels 「統合チャット」 (unified chat). One list holds the tenant's internal channels and the rooms of Slack / Chatwork / LINE / Microsoft Teams / Messenger (Facebook page) connections that were put into it, plus your own Gmail and calendar (Google Calendar / Outlook) once you connect them (an admin or manager turns on 「統合チャットに入れる」 in /settings/chat-surfaces; only an admin can turn it off, which deletes that connection's rooms and their records). The narrow column at the far left picks the source: 「すべて」, 「社内」 (switches to the internal channel list described in the next row), or one connected service (only services that have rooms are shown; on a wide screen each service shows only its logo and 「自分のアカウントをつなぐ」 only its icon — hover for the name). Tabs above the list: 「要対応」, 「未読」, 「顧客別」 (grouped by customer name; rooms without one go last under 「未設定」), and 「ルーム別」 (the default). The search box matches room names and customer names. An open room is held in the URL as ?room=<ルーム ID>. Every message in a room is kept, including ones that did not mention the bot; Slack and Chatwork rooms also bring in the last 7 days when the first member turns their channel or room on (up to 200 messages on Slack, 100 on Chatwork), Chatwork rooms then bring in new messages every 5 minutes (mentions of the bot arrive at once), and LINE and Teams rooms show only messages after they were added (the header says 「直近 7 日と接続後の発言」 or 「接続後の発言だけ」). Replying: the input box is labelled 「外部へ送信」 with the destination; Enter or the send button opens a confirmation card (「…に送信します」), and nothing is sent until 「送信する」 is pressed. On a Slack or Teams channel, if you have authorized your own Slack / Microsoft Teams connection (private) in /settings/connections and it reaches that workspace or channel, the reply is posted as you through it; otherwise (and on Chatwork, LINE official accounts, Messenger, Teams group and one-to-one chats) it goes out through the connected bot under your own name (on Slack the sender name is replaced; elsewhere 「名前: 」 is put at the head of the text). Each sent message shows 「送信中」 / 「送信済み」 / 「送信に失敗しました」 with 「もう一度送る」. The agent cannot send to these rooms — only a person can, from this screen. AI labels and 「要対応」: about a minute after a new message in a room, AI reads the room and labels it 「要対応」 (a request or question from the other side is still unanswered), 「返信待ち」 (waiting for their answer to our question or proposal), or 「確認のみ」 (nothing needs a reply); hovering the label shows what it means. The 「要対応」 tab lists only 「要対応」 rooms. Until AI has judged the latest message (or when it cannot), a room is marked 「要対応」 when the last message came from an outside person, and the mark clears when someone (or the agent's reply) answers in the room. Calendar rooms are not judged by AI. 「要対応にする」 in the room header marks it by hand, overriding the AI label, until the next reply, 「要対応から外す」 clears it, including an automatic mark, until the next message from an outside person. 「AI アクセス」 (keep a room away from AI — 「AI に読ませない」 / 「AI に渡したくない」 is this switch turned OFF): the room header's 「AI アクセスを OFF にする」 button stops AI from receiving anything from that room — no AI label (「要対応」 falls back to the last-message rule above), and the AI bot does not answer there (whoever mentioned it gets a private note 「このルームは AI アクセスが OFF のため、AI は返答しません」, or nothing on a surface with no private destination); the room shows an 「AI アクセス OFF」 tag, messages are still kept and replies still work, and 「AI アクセスを ON にする」 undoes it. It can also be set per connection, covering every room of it including later ones: an admin only switches 「AI アクセス」 off from the row's 「⋯」 in /settings/chat-surfaces (shown for connections in the unified chat), and the person who connected a Gmail switches 「AI アクセス」 off on its row under 「つないでいる Gmail」 in 「自分のアカウントをつなぐ」. While it is off at the connection level, the room's button is disabled. Content already handed to AI before it was switched off is not taken back. Calendar rooms have no such button (they are never judged). If a colleague is treated as outside, choose 「この人は社内」 from the 「⋯」 on their message (「社内の印を外す」 undoes it). 「顧客名を付ける」 in the header sets the customer name used by 「顧客別」 (up to 40 characters). The refresh button (a circular arrow at the right of the room header, named 「更新」; Slack, Chatwork, Gmail, calendars, and Messenger; not LINE or Teams) fetches new messages from the service, at most once a minute. Gmail and calendars are also fetched when the screen opens and about every 15 minutes in the background. Messages in a room can be saved to 「あとで」, and threads open in a pane on the right. Quotes and the original message: in a Gmail room the quoted earlier mail is folded so only the reply shows; 「引用を表示」 under the text opens it. Hovering a message shows 「元のメッセージを開く」, which opens that message in the original service in a new tab — for Gmail and Chatwork messages; for Slack it opens the channel the message is in (not other services). Gmail (「自分のアカウントをつなぐ」): the left column shows a 「Gmail」 tag and a 「自分のアカウントをつなぐ」 button; the sheet has a 「メール」 and a 「カレンダー」 section. The 「メール」 section connects your own Gmail (the main threads, not promotions or social) through a Gmail connection you authorized yourself (private) in /settings/connections — the sheet lists each such connection by name with 「この Gmail をつなぐ」; with none it shows only the link 「連携の画面で Gmail をつなぐ」. The first load brings in the latest 30 threads of the last 7 days; later fetches are incremental. Each thread is a room (the subject is the room name; bodies are cut at 20,000 characters). Reply goes to the sender of the latest message from someone else (its Reply-To if present), with the other To/Cc people on Cc, under the same thread, and the confirmation card shows 宛先 / Cc / 件名 before 「送信する」; a thread with only your own messages has nobody to reply to. If the connection's authorization lapses, or you unlink or delete it in /settings/connections, the left column shows a 「Gmail を再認可」 link (「再認可」 under the logo on a wide screen) and the sheet says 「Gmail の再認可が要ります」 with a 「再認可」 link — both open /settings/connections, where you authorize it again (relinking brings the Gmail back). Deleting the connection removes its rooms. 「この Gmail を切断します」 removes its rooms from the list (mail in Gmail stays). Calendar (Google Calendar / Outlook, the sheet's 「カレンダー」 section): connects your own default calendar (Google's primary calendar, Outlook's default calendar). It only receives — you cannot reply or answer an invitation (accept / decline) from these rooms. It uses a Google Calendar or Outlook connection you authorized yourself (private) in /settings/connections (the same connections the /calendar sync uses); the section lists each one with 「この Google カレンダーをつなぐ」 / 「この Outlook カレンダーをつなぐ」, and with none it shows only the link 「連携の画面で Google カレンダーか Outlook をつなぐ」 (「つないでいます」 once connected; 「つないでいますが、再認可が要ります」 if its authorization lapsed — same for Gmail). An Outlook account whose own e-mail address cannot be read is refused (「このカレンダーの持ち主のメールアドレスを読み取れなかったため、つなげませんでした。…」). Two kinds of rooms: 「今日の予定(<the calendar's address>)」, one per calendar — each day it gets one message listing that day's events (14:00〜15:00 件名(場所), all-day events marked 「終日」), and a second 「今日の予定(更新)」 only when the list changes; it first appears on a day that has events, after which an empty day says 「今日の予定はありません」; it is never marked 「要対応」. One room per invitation — an event someone else organizes, that you are invited to, have not declined, and that has not ended (a recurring series is a single room). When the organizer changes its title, time, or place, or cancels it, one message is added (「変更」 / 「取り消し」); other attendees' responses add nothing. An invitation from an outside organizer is marked 「要対応」; one from a member is not. The first load brings in invitations starting within the next 30 days, nearest first, up to 30 rooms; past events are not imported (the header says 「今日の予定と、30 日先までの招待」). Instead of the input box the room says 「カレンダーのルームからは返信できません。出欠は Google カレンダーで返してください。」 (「…Outlook で…」 for Outlook) — answer in the calendar itself. 「あとで」, customer names, 「この人は社内」, and 「要対応」 work as in other rooms. Outlook times are shown in Japan time. Each connected calendar shows its logo in the left column; when it needs re-authorization, a 「Google カレンダーを再認可」 / 「Outlook カレンダーを再認可」 link appears there, and 「カレンダーの再認可が要ります」 / 「再認可」 in the sheet's 「つないでいるカレンダー」 list. 「切断」 there (confirm 「このカレンダーを切断します」) removes its rooms from the list (the events in the calendar stay). These rooms are separate from Samurai App's own calendar (/calendar, references/webui-calendar.md): connecting here does not import events into it. Personal LINE (the sheet's and the left column's 「LINE(個人)」): connects your own personal LINE account (not an official account), so your LINE chats appear as rooms and you can reply as yourself (no name is added). An admin must first allow it — 「個人の LINE」 in /settings/chat-surfaces, 「メンバーが個人の LINE をつなぐことを許可する」 (off by default; only an admin or owner can change it); until then the sheet has no 「LINE(個人)」 section. In 「自分のアカウントをつなぐ」, the 「LINE(個人)」 section shows three notices: it uses an unofficial method, not one LINE provides; it may violate LINE's terms of use and any effect on your account is your own responsibility; and connecting logs out LINE for Chrome (the smartphone and desktop apps are not affected). Check 「上の注意事項に同意します」 and press 「QR コードを出す」. Scan the QR code with LINE on your smartphone; a number (PIN) then appears on the sheet — enter it in LINE on the smartphone, and the sheet says 「つながりました」. If the QR code does not appear, the admin has not allowed personal LINE (no 「LINE(個人)」 section), or the notices have not been agreed to (the button stays disabled). If it fails or expires (「QR コードの有効期限が切れました。…」), press 「QR コードを出し直す」. A LINE account already connected by someone else is refused (「この LINE アカウントはすでにつながっています。」), and reconnecting with a different LINE account than before is refused too — disconnect first. On connecting, the last 7 days (up to 200 messages, 50 chats) are brought in once; after that new messages arrive as they are sent (there is no 「更新」 for these rooms). Each chat (one-to-one or group) is a room only you can read and send in. Images, stickers, and other non-text messages show as 「[画像]」 「[スタンプ]」 etc.; a Letter Sealing message that could not be decrypted shows as 「[暗号化を解除できなかった発言]」. Reading a room does not mark it read in LINE. A reply that does not finish within 30 seconds shows 「送信に失敗しました」 — it may still have reached the other person, so check in LINE before 「もう一度送る」. If you log in to LINE for Chrome again, the connection stops: the left column shows 「LINE を再接続」 (「再接続」 on a wide screen) and the sheet's 「つないでいる LINE」 list says 「再接続が必要です」 — press 「もう一度つなぐ」 and scan a new QR code. 「切断」 (confirm 「この LINE を切断します」) removes its rooms and their records from the unified chat; the chats in LINE stay. If the admin turns the setting off, every member's personal LINE is disconnected and its rooms are removed. Personal LINE messages are never handed to the agent, and outside AI (MCP, the CLI) cannot read these rooms. Messenger: a Facebook page connected in /settings/chat-surfaces always goes into the unified chat (it cannot be switched off). Customers can reply only within 24 hours of their last message; after that the input is replaced by a note, and a room that has received nothing is also closed. A reply is at most 2,000 characters. Messenger messages are never handed to the agent (no mention path). Your own sends from the Page inbox appear in the room too. Real customers need Meta's App Review (pages_messaging Advanced Access); until then only the app's admins, developers, and testers can talk to the page. Who can read: a group or channel room is open only to the members who turned it on in 「受信するチャンネルを選ぶ」 (below); one-to-one rooms (such as a LINE official account's chats or a Messenger page) only to the person who registered that connection; a Gmail room, a calendar room, or a personal LINE room only to the person who connected it. Setting it up in /settings/chat-surfaces: Admins and managers can turn on 「統合チャットに入れる」 from the row's 「⋯」 (the row then shows a 「統合チャット」 badge): every message there is kept as a room in /channels, where people can read and reply. The setup steps for the extra events and permissions appear on screen (Slack: the app must be reinstalled with the added scopes). Each member chooses the channels they receive — there is no channel choice in /settings/chat-surfaces. In /channels, 「受信するチャンネルを選ぶ」 in the far-left column (an icon of a checklist on a wide screen) opens a sheet listing, per connection, only the channels the shared bot is in and that you yourself are a member of in the original service (Slack channels where the bot was invited and someone has spoken, Chatwork group rooms the bot account has joined, LINE groups, Teams channels); channels you are not in are not listed at all. Turn a switch on to receive that channel as a room; only the members who turned it on can read and reply in it. Checking membership needs your account linked to the service (「自分の紐付け」 in /settings/chat-surfaces; mention the bot in that service to get the linking message) — without it the sheet says the account is not linked and links to 「自分の紐付けを見る」. Channels whose membership could not be checked are shown only as a count with 「再試行」. Until someone turns a channel on, its messages are not kept. When the last member turns it off, the room and its records are deleted. Membership is re-checked every hour: anyone who left the channel in the original service (or whose link was removed) stops receiving it, and a reply from someone who is no longer a member is refused (「このチャンネルに参加していないので送れません。…」). Removing a member from the tenant also removes their choices. Direct messages and one-to-one chats (Slack DMs, LINE one-to-one, Teams personal chats, Messenger) need no choosing and become the connection owner's room. Messenger: choose Messenger and pick the page's access token and app secret from the tenant-shared secrets (the page is read from the token, so no page ID is entered); after creating it, the row shows 「Webhook の URL と確認トークン」 (the verify token is generated for you; re-open it from the row's 「Webhook の URL を見る」 — admins only) to paste into the Meta app's Messenger Webhook settings, subscribing to messages and message_echoes. A Messenger page is always in the unified chat; if it was detached (e.g. after a member was removed), recreate it. 「個人の LINE」 (a section of that screen): 「メンバーが個人の LINE をつなぐことを許可する」 lets members connect their own personal LINE to the unified chat through an unofficial method — off by default; only an admin or owner can change it. Turning it off (confirm 「個人の LINE の許可をオフにします」) disconnects every member's personal LINE and removes those rooms and records (the chats in LINE stay); turning it back on restores nothing until each member reconnects. To read Gmail and calendars in the unified chat, each member first authorizes their own Gmail / Google Calendar / Outlook connection in /settings/connections, then connects it with 「自分のアカウントをつなぐ」 in /channels; no OAuth app has to be registered. Calendar rooms are receive-only (no replies or RSVPs).
/channels → 「社内」 「チャンネル」 (channels). Choose 「社内」 in the far-left column to get the channel list with its row menus, threads, and the notification button; the right side is its contents, and the open channel is held in the URL as ?channel=<チャンネル ID>. Create a channel with the 「+」 at the top of the left column. When creating it, choose who can join: 「テナントの全員」 or 「選んだグループと人だけ」 (pick groups and individual people; you are always included). A restricted channel does not appear in anyone else's list and cannot be opened by them, even with its URL; it shows a lock in the list and 「参加者限定」 next to its title. The creator and administrators can change the participants later from the row's 「⋯」 → 「参加者を変える」 — removed people can no longer read any of its past messages, and added people can read the past messages too. Files uploaded in a channel can be opened only by its current participants (in an open channel, that is everyone, but other people do not see them in their own /files). Restricting an open channel later also closes the files uploaded there before to its participants and the uploader — except files moved into a folder, shared by link, or also attached in another conversation. Type 「@」 in the input box to mention a participant (only the channel's participants are offered; mentioning someone else does nothing). A channel holds 0 or more bots (header button; creator/admins manage; shared and standard bots only): a bot named with 「@」 always answers, otherwise the main bot answers only when it judges that it has been called, and with no bots it is a members-only chat. A bot's reply can also 「@」 a person or another bot in the channel — a mentioned person gets the same notification as any mention, and a mentioned bot answers next, with the permissions of the person who started the exchange. How many times bots can hand off to each other after a person's message is capped per channel (default 5, 0–20; 0 means bots never call each other; the creator and administrators change it in the bot settings from the header button, others only see it). As grounds for its answers it can draw on reads only (web, knowledge, files, tables, procedures); it neither writes nor runs apps. Since it can read procedures, "follow this procedure" works, but it cannot create a new procedure. A reply grounded in documents or tables visible only to one individual is hidden from other members until the person who cited them allows it to be shown. Each message shows its time next to the sender's name, messages are divided by day (「今日」 / 「昨日」 / date), and consecutive messages from the same sender within 5 minutes are grouped under one name. You can add emoji reactions to messages (from the face icon that appears at the corner of a bubble when you point at the message or move keyboard focus to it — on touch screens it is always shown below the bubble. You can choose from all emoji and search in Japanese) — you can only remove the ones you added yourself, and the agent also occasionally adds just a reaction to a message that doesn't warrant a reply. The creator and administrators can rename or delete a channel (from the 「⋯」 on its row in the list — it appears when you point at the row or the row is open, and is always shown on touch screens. Deleting removes all its messages and threads). Threads: 「この発言からスレッドを作成」 next to that face icon starts one (one per message) — the message is copied into it. Threads sit indented under their channel and share its participants, bots, and notifications. Opening a thread from the entry under its message keeps the channel open and shows the thread in a pane on the right (on a narrow screen the thread alone), with 「全画面で開く」 to show the thread by itself and × to close it; opening a thread from its row in the list shows it full-screen, with a back button to the parent. Each thread row shows the icons of the people who posted in it (most recent first, up to 3, then 「+N」). Links: pasting an in-app link (a file, a SIROE page, and so on) into the channel input box turns it into a named chip, as in the regular chat. 「リンクをコピー」 in the bar that appears on a message copies that message's URL (/channels?channel=<チャンネル ID>&message=<メッセージ ID>); opening it scrolls to the message and briefly highlights it. A pasted message URL shows a card under the message (channel name, sender, time, the start of the text; clicking it jumps there) — the card is drawn for each viewer, so a message the viewer cannot see shows 「このメッセージは表示できません」 instead. Notifications are chosen per channel from that 「⋯」 → 「このチャンネルの通知」: 「すべての発言」, 「メンションされたときだけ」 (the default), or 「通知しない」. In a restricted channel the notification says only who posted, not the message text
/channels → 「社内」, when an operation fails A refusal shows the reason and what to do next, with a small line beneath it: 「エラーコード: CH-40401 ・ 問い合わせ番号: 7f3a9c21」 (the code names the cause; the request number identifies that one request). When asking support about a failure, pass both — support finds the cause and the log line from them. The line can be selected and copied. A failure that never reached the server (the connection dropped) has neither, so the line is absent