apps`)

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.

「データ」 — skills and apps

Where What you can do

/settings/skills Business skills; /settings/skills/<名前> is one. Row 「…」: display name, icon, labels, 「自分だけ無効にする」 / 「有効に戻す」 (anyone), 「全員に対して無効にする」 (admins and managers; tenant-wide and bundled skills only), and delete (not for bundled skills; 「スキルにする」「ブラウザ操作の手引き」「連携した SaaS を操作する」 cannot even be disabled). Tenant-disabled rows lack 「自分だけ〜」 (not overridable). Both 「〜無効にする」 confirm first; turning back on does not. The skill page's header has the same two in one 「無効にする」 menu. Check rows to disable (for yourself), re-enable, or delete in bulk. The detail has these switches by its name (re-enable there), 「手順を編集」 or 「自分用に編集する」, and a 「…」 to change display name, icon, labels, and code (「コードを編集」). 「チャットで直す」 (own skills) opens a chat to change it: say what to change, no input file needed. 「複製して直す」 (shared ones too) copies it whole under a new name, keeps the original, and opens that chat; 「複製だけする」 in the same dialog copies without opening one. Not for bundled or disabled skills. The procedure panel's 「ワークフローを作る」 turns the steps into a draft workflow and opens it (not for disabled skills). Your own skills can be shared tenant-wide or to a group (members included; sharing copies, yours stays; the row's 「…」 → 「<宛先>の共有をやめる」 deletes the copy you shared). Details have 「バージョン履歴」, even without scripts: one per edit or approved update from chat, newest 20 kept (fewer if very large). A version's 「変更を見る」 diffs it against the current one (body, steps, scripts); 「戻す」 restores it entirely (anyone who can edit; it discards everyone's unsaved drafts). The same works from chat: 「前のバージョンに戻して」 makes the agent list the versions and roll back after you approve its card. Updating never overwrites — the update proposal card says so, so there is no need to copy a skill before changing it. Files a skill's pre-save trial run newly writes go to tmp/ (collapsed in the file list, deleted after 7 days); a file it overwrote keeps its name. A skill can carry images and files (a sample image, an Excel template): open the editor with 「ファイルを追加」 (「コードを編集」 for a skill with scripts) in the skill's menu, then 「画像やファイルを追加」, then 「保存」. PNG, JPEG, GIF, WebP, SVG, PDF, Excel, PowerPoint, Word, CSV, and fonts, up to 10 MiB each and 30 MiB per skill; file names in ASCII letters and digits. The skill detail lists them under 「同梱している画像やファイル」. In chat, asking for a skill can also put an attached file into its proposal card. A refused skill change shows the reason and next step, with a small line: 「エラーコード: SK-40013 ・問い合わせ番号: 7f3a9c21」 — pass both when asking support. For example: the edited script has not been tried yet (SK-40013: press 「試す」 first), or a skill with the same name exists (SK-40901). When a file, step, input, or 「使う操作」 check fails, the check's own reason appears on one line between the two. 「使う操作」 lists the exact operation keys a skill uses (browser keys name a site, such as browse:commit@example.com; wildcards, unsaved drafts, and operations that always ask a person cannot be listed). Asking in chat to stop being asked about an operation can also put it on the skill's proposal card, where you read it before adding the skill. The first time someone opens that version, a card asks 「このスキルが使う操作を許可しますか」. If they allow it, those operations skip the approval card until that request ends; a later request has to open the skill again. Declining still opens the skill and each operation asks as usual. Saving the list makes a new version, as does editing the body, steps, or files, so everyone is asked again. Labels and saved-time figures do not make a version, and 「戻す」 returns to an old version with the answers it already had. The card can only be allowed on the screen: over MCP or the CLI it can only be declined. Operations an admin has set to deny or to always ask stay that way. 「使う操作」 shows your own answer per row; 「答えを取り消す」 clears it for all versions, even without edit rights, and the card asks again.

/apps 「アプリ」. /apps/<アプリ ID> is a single app; /apps/<アプリ ID>/edit is the editor (on a wide screen, 「チャットを重ねる」 beside the 「チャット」 / 「プレビュー」 tabs floats the chat over the code so the preview stays open; 「右の列に戻す」 puts it back — same in a skill's editor). A deleted app stays in the trash (/apps/trash) for 90 days; its creator presses 「復元」 there to get it back with all its versions (own apps only, several by checking; no permanent delete). On /apps/<アプリ ID>, the tag next to the name opens the visibility level, 「外部公開」 and 「他の人にも実行を許可する」 (creator only). 「コードを編集」, 「表示名を変更」, 「説明を変更」, 「アイコンを変更」 and 「アプリを削除」 are in the 「…」 at the top right. Row 「…」: 「コピーを作成」, 「削除」. The list filters by title, identifier, category, label, both kept in the URL. The 「ラベル」 column on the left (chips above the list on a narrow screen) lists 「すべてのアプリ」, each label's count, and 「ゴミ箱」; clicked labels narrow to apps having all of them (click again to remove). A card's 「…」 or right-click offers 「開く」 / 「表示名を変更」 / 「説明を変更」 / 「アイコンを変更」 / 「ラベルを変更」 (disabled with the reason on others' apps). Checked cards go to the trash with 「まとめて削除」 (own apps only). An app whose buttons no longer match their table (a required column without input, or a missing column) shows 「要修正」, naming each button and the reason to people who can write the table (a deleted table, to everyone); its creator fixes it in chat. Only the creator edits the icon (a fixed set), labels (「+」 under the name picks or types one), name, and description. The description shows under the name (the agent's while empty). Visibility levels: 「自分のみ」 / 「グループ」 / 「テナント全体」. Publishing externally opens it to people not signed in at /p/<公開 ID>. Tabs: 「アプリ」 / 「利用の記録」 / 「会話」 / 「設定」; 「設定」 holds the embed tag for a registered site, credentials lent to server functions, and approved keys; notices sit below the app. A refused app change shows the reason and next step, with a small line: 「エラーコード: AP-40901 ・問い合わせ番号: 7f3a9c21」 — pass both when asking support. For example: someone saved meanwhile (AP-40901: reload, then save), or the app was deleted (AP-40401). A build error's line and column show in the editor's top bar

Where	What you can do
`/settings/skills`	Business skills; `/settings/skills/<名前>` is one. Row 「…」: display name, icon, labels, 「自分だけ無効にする」 / 「有効に戻す」 (anyone), 「全員に対して無効にする」 (admins and managers; tenant-wide and bundled skills only), and delete (not for bundled skills; 「スキルにする」「ブラウザ操作の手引き」「連携した SaaS を操作する」 cannot even be disabled). Tenant-disabled rows lack 「自分だけ〜」 (not overridable). Both 「〜無効にする」 confirm first; turning back on does not. The skill page's header has the same two in one 「無効にする」 menu. Check rows to disable (for yourself), re-enable, or delete in bulk. The detail has these switches by its name (re-enable there), 「手順を編集」 or 「自分用に編集する」, and a 「…」 to change display name, icon, labels, and code (「コードを編集」). 「チャットで直す」 (own skills) opens a chat to change it: say what to change, no input file needed. 「複製して直す」 (shared ones too) copies it whole under a new name, keeps the original, and opens that chat; 「複製だけする」 in the same dialog copies without opening one. Not for bundled or disabled skills. The procedure panel's 「ワークフローを作る」 turns the steps into a draft workflow and opens it (not for disabled skills). Your own skills can be shared tenant-wide or to a group (members included; sharing copies, yours stays; the row's 「…」 → 「<宛先>の共有をやめる」 deletes the copy you shared). Details have 「バージョン履歴」, even without scripts: one per edit or approved update from chat, newest 20 kept (fewer if very large). A version's 「変更を見る」 diffs it against the current one (body, steps, scripts); 「戻す」 restores it entirely (anyone who can edit; it discards everyone's unsaved drafts). The same works from chat: 「前のバージョンに戻して」 makes the agent list the versions and roll back after you approve its card. Updating never overwrites — the update proposal card says so, so there is no need to copy a skill before changing it. Files a skill's pre-save trial run newly writes go to `tmp/` (collapsed in the file list, deleted after 7 days); a file it overwrote keeps its name. A skill can carry images and files (a sample image, an Excel template): open the editor with 「ファイルを追加」 (「コードを編集」 for a skill with scripts) in the skill's menu, then 「画像やファイルを追加」, then 「保存」. PNG, JPEG, GIF, WebP, SVG, PDF, Excel, PowerPoint, Word, CSV, and fonts, up to 10 MiB each and 30 MiB per skill; file names in ASCII letters and digits. The skill detail lists them under 「同梱している画像やファイル」. In chat, asking for a skill can also put an attached file into its proposal card. A refused skill change shows the reason and next step, with a small line: 「エラーコード: SK-40013 ・問い合わせ番号: 7f3a9c21」 — pass both when asking support. For example: the edited script has not been tried yet (SK-40013: press 「試す」 first), or a skill with the same name exists (SK-40901). When a file, step, input, or 「使う操作」 check fails, the check's own reason appears on one line between the two. 「使う操作」 lists the exact operation keys a skill uses (browser keys name a site, such as `browse:commit@example.com`; wildcards, unsaved drafts, and operations that always ask a person cannot be listed). Asking in chat to stop being asked about an operation can also put it on the skill's proposal card, where you read it before adding the skill. The first time someone opens that version, a card asks 「このスキルが使う操作を許可しますか」. If they allow it, those operations skip the approval card until that request ends; a later request has to open the skill again. Declining still opens the skill and each operation asks as usual. Saving the list makes a new version, as does editing the body, steps, or files, so everyone is asked again. Labels and saved-time figures do not make a version, and 「戻す」 returns to an old version with the answers it already had. The card can only be allowed on the screen: over MCP or the CLI it can only be declined. Operations an admin has set to deny or to always ask stay that way. 「使う操作」 shows your own answer per row; 「答えを取り消す」 clears it for all versions, even without edit rights, and the card asks again.
`/apps`	「アプリ」. `/apps/<アプリ ID>` is a single app; `/apps/<アプリ ID>/edit` is the editor (on a wide screen, 「チャットを重ねる」 beside the 「チャット」 / 「プレビュー」 tabs floats the chat over the code so the preview stays open; 「右の列に戻す」 puts it back — same in a skill's editor). A deleted app stays in the trash (`/apps/trash`) for 90 days; its creator presses 「復元」 there to get it back with all its versions (own apps only, several by checking; no permanent delete). On `/apps/<アプリ ID>`, the tag next to the name opens the visibility level, 「外部公開」 and 「他の人にも実行を許可する」 (creator only). 「コードを編集」, 「表示名を変更」, 「説明を変更」, 「アイコンを変更」 and 「アプリを削除」 are in the 「…」 at the top right. Row 「…」: 「コピーを作成」, 「削除」. The list filters by title, identifier, category, label, both kept in the URL. The 「ラベル」 column on the left (chips above the list on a narrow screen) lists 「すべてのアプリ」, each label's count, and 「ゴミ箱」; clicked labels narrow to apps having all of them (click again to remove). A card's 「…」 or right-click offers 「開く」 / 「表示名を変更」 / 「説明を変更」 / 「アイコンを変更」 / 「ラベルを変更」 (disabled with the reason on others' apps). Checked cards go to the trash with 「まとめて削除」 (own apps only). An app whose buttons no longer match their table (a required column without input, or a missing column) shows 「要修正」, naming each button and the reason to people who can write the table (a deleted table, to everyone); its creator fixes it in chat. Only the creator edits the icon (a fixed set), labels (「+」 under the name picks or types one), name, and description. The description shows under the name (the agent's while empty). Visibility levels: 「自分のみ」 / 「グループ」 / 「テナント全体」. Publishing externally opens it to people not signed in at `/p/<公開 ID>`. Tabs: 「アプリ」 / 「利用の記録」 / 「会話」 / 「設定」; 「設定」 holds the embed tag for a registered site, credentials lent to server functions, and approved keys; notices sit below the app. A refused app change shows the reason and next step, with a small line: 「エラーコード: AP-40901 ・問い合わせ番号: 7f3a9c21」 — pass both when asking support. For example: someone saved meanwhile (AP-40901: reload, then save), or the app was deleted (AP-40401). A build error's line and column show in the editor's top bar

Using one skill in several stores or sites — update or duplicate

Recommended: keep 1 skill and update it; duplicate only for a store whose procedure really differs.

Same procedure in every store → 1 shared skill, updated in place. Share it tenant-wide (or to the group covering the stores) and improve that one (「チャットで直す」). Every store gets the fix at once, and nothing is lost — 「バージョン履歴」 keeps the newest 20 and 「戻す」 restores one. Copies have to be fixed one by one and drift apart
Keep store-specific values out of the body. Store name, store code, folder, sheet: have the skill ask for them at the start, or read them from a table with a store column (ask for that in 「チャットで直す」). For files on each store's PC, register the same folder layout and use relative paths (references/cli.md), so 1 skill works on every PC
A store whose procedure really differs → 「複製して直す」. The copy is a separate skill (rename it in 「…」, e.g. 「売上集計(渋谷店)」), and later fixes to the original do not reach it
A small tweak of a shared skill for yourself → 「自分用に編集する」. It covers the shared one under the same name; when the shared one is updated, 「共有元のバージョンが更新」 appears, but nothing merges — delete your version to go back
Do not share same-named versions to different store groups. A person in 2 groups that both hold the name gets neither (the list names the clash)

#Using the WebUI — skills and apps (/settings/skills, /apps)

#「データ」 — skills and apps

#Using one skill in several stores or sites — update or duplicate

Using the WebUI — skills and apps (`/settings/skills`, `/apps`)

「データ」 — skills and apps

Using one skill in several stores or sites — update or duplicate