8.1. Integrated Services
Overview
AAS does not work alone. It works by connecting to several services. This chapter summarizes what users experience when an integration is cut, what an administrator can check on the screen, and what to report to the operator.
Permissions: This is content that general users and administrators can see on the screen. Installing and fixing integrations is the operator's work.
The operator is the person who installs AAS and manages the server (see the A.3. Glossary). Server installation and configuration are outside the scope of this manual. For installation and changes, ask the operator, or see the AAS installation chapter of the COP (OPENMARU Container Orchestration Platform) installation guide.
Integrated Services at a Glance
| Service | What users experience when it is cut | Where an administrator checks |
|---|---|---|
| SSO (Single Sign-On, the sign-in server) | They cannot sign in. | The message on the sign-in screen, the notice above the "Users & permissions" screen |
| Model server (LiteLLM) | The AI agent does not answer. | "Operations" on the dashboard, "My AI Agents › Models" |
| Skill Hub (SkillHub) | They cannot install skills, and install requests wait. | "Operations" on the dashboard, the "Skill Hub" screen |
| Dictation and read-aloud server | "Voice input" is blocked, or read aloud does not work. | The buttons in the chat message box |
| Internal wiki connection | The AI agent cannot read or write wiki pages. | The profile's MCP server list |
SSO (Single Sign-On)
SSO is a method where you sign in once and use several services. AAS identifies users through a separate sign-in server. When a user goes to the AAS address, they are taken to the sign-in screen. Symptoms of being unable to sign in are in 2.5. Sign-In and Sessions and A.2. Troubleshooting.
| Item | Description |
|---|---|
| Administrator | An administrator is a person who meets one of three conditions: someone who received the administrator role on the sign-in server, someone designated as an administrator on the "Users & permissions" screen, or someone the operator designated as an administrator at installation. |
| Administrator designated at installation | Their permissions cannot be changed, and they cannot be disabled or deleted, on the "Users & permissions" screen. To change them, ask the operator. |
| Installation with sign-in off | Everyone is treated as an administrator. This is for local testing and can be reached only from this computer. "Login is off" appears under the title of the "Users & permissions" screen. |
The operator sets up the roles and groups on the sign-in server. For the on-screen steps to add administrators, see 2.3. Assigning Administrators and Team Managers.
The screen effects related to SSO are as follows.
- The "Claude Code connections" tab appears on the "Users & permissions" screen only in installations where sign-in is turned on.
- Departments are managed on the "Departments" tab of the "Users & permissions" screen.
- The password of the default account created at installation (the name is usually
aas-admin) may be a publicly known value. If this account is on the "Users & permissions" screen, ask the operator whether the password has been changed. The operator changes the password on the sign-in server.
Model Server (LiteLLM)
LiteLLM is a relay server that lets you use several AI models through one address. AI agent chats, auxiliary tasks, and question checks (guardrails) all go through this server.
| Where to check | What you see |
|---|---|
| "Operations" on the dashboard | One of "LiteLLM OK", "LiteLLM unreachable", or "LiteLLM not checked yet" |
| "My AI Agents › Models" | The model list. If the connection cannot be checked, "LiteLLM status unknown" appears. With "Test" you can send one 1-token call to a model (administrators only). |
| Chat | If the model server does not respond, no answer appears. Questions blocked by a guardrail are rejected. |
If "LiteLLM unreachable" appears, tell the operator. When you report it, include the text from "Operations" on the dashboard and the symptom the user experienced. For the model list and connection checks, see 4.1. Models. For checking blocked requests, see 4.2. Safeguards.
Skill Hub (SkillHub)
AAS stores skill packages in the Skill Hub. The hub is used only through the AAS screen.
- The hub has no separate address (web screen). Viewing the list, installing, and publishing are all done on the "Skill Hub" screen of AAS.
- Skill install requests are processed in order by the install helper of the AAS server. If the helper stops, "Skill hub helper stopped" appears in "Operations" on the dashboard. When that happens, tell the operator.
- In an installation where the hub connection is not set, the "Skill Hub" screen shows "The skill hub URL is not set". Tell the operator.
- The AAS server publishes the AAS built-in skills to the hub. See 6.3. Built-in Skills and New Version Notices.
- For the divisions such as shared and restricted, see 6.1. The Skill Hub and Namespaces.
Note: The COP installation guide calls the same component "Skill Market (SkillHub)". It is the same as the "Skill Hub" on the AAS screen.
Dictation and Read-Aloud Server
Dictation and read aloud are optional features. They appear on the screen only if they were turned on at installation. The operator turns them on and off.
| Feature | Screen | When not turned on or when cut |
|---|---|---|
| Dictation | The "Voice input" button in the chat message box. It records up to 1 minute and does not save the recording. | The button is not shown. If "Transcription is busy right now. Select retry" appears, have the user try again after a moment. |
| Read aloud | "Read aloud" under an AI answer, and choosing a voice in "Settings › My display" | Read aloud cannot be used. |
Dictation requires the user's AI agent workspace to be connected. If the workspace is stopped, "Voice input is unavailable because the AI Agent Workspace is not connected" appears. In that case, see 3.2. Workspace Status and Restarting. If an inquiry says the button is missing, ask the operator whether dictation was turned on in the installation.
Internal Wiki Connection
You can let a user's AI agent read and write pages in the internal wiki (Docmost, Outline). The user adds the wiki's MCP (Model Context Protocol) server in their profile to connect it. For the on-screen steps, see 5.7. Internal Wiki Connection Skills in the User Manual. There are three points for an administrator to know.
| Item | Description |
|---|---|
| Key | Each user enters their own key. A shared service account key is not used. |
| Permissions | The wiki decides. The AI agent does only what the user who entered the key can do in the wiki. |
| Writing | At first only reading is on. The user turns on writing separately. |
Warning: Even when another person gives this AI agent work in the Office or a meeting room, it writes to the wiki with the permissions of the user who entered the key. Tell users who turn on writing about this.