What an Administrator Can Do

The platform is already installed for you. What is left is turning it, in your browser, into something your company actually uses — build assistants, feed them company documents, open them to staff, cap the spend, keep the records.

Before you start

• You have an administrator account. After signing in, an「Admin」section appears on the left. If it is missing, you are currently signed in as a regular employee — contact the person who handled your rollout.
• Installing and configuring the platform is not covered in this manual, and you do not need to do any of it. This track only covers what you can click on screen.
• You do not need to write code. Every chapter below is clicking buttons and filling in fields.

Step 1 · Learn the left-hand menu

After signing in, the left-hand navigation is fixed. The upper half holds the everyday features everyone gets; only the lower half, marked「Admin」, is the administration area.

Everyday features (visible to the whole company)

Menu	What it does
「對話」(Chat)	The main screen for talking to an AI assistant. The primary entry point for staff.
「我的看板」(My Board)	One place for personal tasks and notifications.
「Nova App」	The app marketplace, where staff open the apps you publish.

Admin (visible to administrators only)

Menu	What it does	Chapter
「初始設定」(Initial Setup)	The setup wizard used during rollout. Your rollout team has usually finished this already, so you do not need to run it again.	—
「總覽」(Overview)	The home page for overall platform status.	—
「戰情室」(War Room)	Watch in real time what your Agents are working on.	—
「Agent 管理」(Agent Management)	Create, configure, and publish AI assistants. The page you will visit most.	Chapter 7
「檔案與知識庫」(Files & Knowledge Bases)	Upload company documents, mount cloud folders.	Chapter 8
「資料集」(Datasets)	Structured business tables (attendance, cases, expense claims…).	Chapter 10
「員工名錄」(Employee Directory)	Import your staff list, manage identity bindings and deactivation.	Chapter 9
「組織架構」(Org Structure)	The department tree. Built automatically when you import staff by CSV.	Chapter 9
「MCP 管理」(MCP Management)	The list of connections to outside systems. Once your rollout team or IT adds one, it shows up in an Agent’s selection list.	—
「技能管理」(Skill Management)	Skill packages an Agent can be given.	Chapter 10
「用量與費用」(Usage & Cost)	How much you spent this month, and which Agent spent the most.	Chapter 11
「稽核紀錄」(Audit Log)	Who did what to which Agent, and when.	Chapter 12
「Runtime 管理」(Runtime Management)	The execution environment behind your Agents. Configured during rollout; no day-to-day changes needed.	—
「進階設定」(Advanced Settings)	Platform-level settings and enterprise sign-in. Ask your rollout contact before changing anything.	—
「應用中心」(App Center)	Ready-made HR / finance / sales App Packs, enabled in one click.	Chapter 10

Step 2 · Be clear on what staff see versus what you see

This is the easiest thing to get wrong: regular employees cannot see the Admin section at all — not even the heading. Their left-hand menu holds only「對話」(Chat),「我的看板」(My Board), and「Nova App」.

「用量與費用」(Usage & Cost) and「稽核紀錄」(Audit Log) have one more layer of protection: even if an employee types the address directly, the page shows「需要管理員權限」(Administrator access required) and no numbers at all.

Put another way:

• Staff see the results (an assistant they can talk to, an app they can open).
• You see the settings and the ledger (who may use it, what it costs, what gets recorded).

So “an employee says they cannot see that assistant” is usually not a fault — that Agent has not been published yet, or the person is not in its access group. Chapter 7 covers both.

Step 3 · Roll out in the recommended order

Do not turn everything on at once. This order is designed so you see a result at every step:

1. Build one Agent and talk to it yourself in the browser. (Chapter 7) No data attached, no channels open — confirm only that it answers in the persona you wrote.

2. Feed it one company document. (Chapter 8) Pick the document people ask about most — leave policy, expense rules. Then ask a question only that document can answer.

3. Set the access group and the usage cap, then publish. (Chapter 7, Chapter 11) Leaving either blank blocks publishing, and that is deliberate: no Agent goes live without an owner and a budget ceiling.

4. Import your staff list and open one channel to a small group. (Chapter 9) Start with 5–10 colleagues and run one department’s Discord or Slack channel for two weeks.

5. Confirm that usage and cost match expectations. (Chapter 11) Look at「用量與費用」(Usage & Cost) and estimate what a company-wide rollout would cost.

6. Open it to the whole company, and confirm your audit and protection settings. (Chapter 12) Set PII masking, blocked words, and audit retention before the crowd arrives.

7. To move faster, use an App Pack to cover the remaining departments in one click. (Chapter 10)

How you know it worked

• After signing in, you can see the「Admin」heading on the left with the full list of menu items beneath it.
• Click「Agent 管理」(Agent Management); the page title reads「Agent 管理」and there is a「＋ 建立 Agent」(Create Agent) button in the top right.
• Click「用量與費用」(Usage & Cost); you can see the「總費用 Total Cost」card (in a new environment the number is 0, which is normal).

Common problems

Symptom	Cause / fix
No「Admin」section on the left	You are signed in as a regular employee. Ask your rollout contact to change your account to administrator.
Clicking「用量與費用」(Usage & Cost) shows「需要管理員權限」(Administrator access required)	Same as above — these two pages are administrator-only.
Fewer menu items than this manual lists	Some menu items stay hidden until rollout configuration is complete, and appear once it is. Contact your rollout contact.
Unsure whether a menu item is safe to click	「Runtime 管理」(Runtime Management) and「進階設定」(Advanced Settings) affect Agents that are already live — ask your rollout contact before changing them. Every other menu is safe to look at as long as you change nothing.
An employee says they cannot see the assistant you just built	That Agent is still in「草稿」(Draft), or the person is not in its access group. See Chapter 7.