> ## Documentation Index > Fetch the complete documentation index at: https://docs.stmlink.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > 对外开放的服务端接口有两组前缀，都用同一套鉴权：`/server/v1/...`（SRTC 与 SMeeting 的主接口）和 `/stm/srvapi/v1/...`（SMeeting 的用户体系，服务端极简对接会用到）。鉴权是 app_id + nonce + timestamp + signature 四个请求头，用 app_key 做 HMAC-SHA256 签名，只能从业务方自己的后端调用。除这两组前缀外的接口均为内部接口，不要建议客户调用。 Public server APIs use two path prefixes with the same authentication: `/server/v1/...` (the main APIs of both SRTC and SMeeting) and `/stm/srvapi/v1/...` (the SMeeting user system, used by server-side low-code integration). Authenticate with four request headers, app_id + nonce + timestamp + signature, where signature is HMAC-SHA256 keyed with app_key; call these APIs only from the customer's own backend. Any other path is internal: never suggest calling it. > app_key 是服务端密钥，绝不能出现在客户端代码、前端配置或移动 App 里。客户端加入频道用的 token 必须由业务方后端签发后下发（SRTC 走 `/server/v1/channel/grant`，SMeeting 走 `/stm/srvapi/v1/member/grant`）。 app_key is a server-side secret and must never appear in client code, frontend config, or a mobile app. The token a client uses to join must be issued by the customer's backend and passed down to the client (SRTC: `/server/v1/channel/grant`; SMeeting: `/stm/srvapi/v1/member/grant`). > SRTC 与 SMeeting 是上下两层不同的产品，术语不通用：SRTC 是音视频底座，说「频道 channel」「加入 / 退出」；SMeeting 建在 SRTC 之上，说「房间 room」「会议 meeting」「进入 / 退出」。回答时按用户所在的层用对应术语，不要把「房间」「会议」安到 SRTC 的接口上，也不要用「频道」「加入 / 离开」描述 SMeeting 的概念（接口标识符原样保留）。 SRTC and SMeeting are two separate layers with different terminology. SRTC is the audio/video foundation: it has channels, and users join and leave a channel. SMeeting is built on top of SRTC: it has rooms and meetings, and members enter and exit a meeting. Answer in the terms of the layer the user is working with: never apply "room" or "meeting" to SRTC APIs, and never describe SMeeting concepts in prose with "channel", "join", or "leave" (API identifiers such as `force_join` keep their literal names). > 同一能力在各端 SDK 里的包名、类名、方法名并不相同。写示例代码时请使用文档中该端自己的 API，不要把一个端的写法套到另一个端上。苹果平台每个产品都有两套 SDK（Swift 原生与 Objective-C），两套 API 不能混用。 Package, class, and method names differ between platform SDKs for the same capability. In sample code, use the API documented for that platform; never carry one platform's code over to another. On Apple platforms each product ships two SDKs (native Swift and Objective-C) whose APIs must not be mixed. # Admin console features > What the built-in admin console does, menu by menu with screenshots: usage stats, channel and meeting management, in-meeting controls, recording, devices, contacts, VOD, licensing, accounts, and media node and gateway operations. Read when evaluating the product or preparing training. Every platform comes with a web-based **admin console** (after deployment, open `https:///admin/`). Administrators can manage apps, meetings, recording, devices, and servers without writing code. Switch the **app** in the lower-left corner: audio and video apps (SRTC) and meeting apps (SMeeting) show slightly different menus. ![Admin console home](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/images/admin-home.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=1381642e591314bed7e4c41989e2c49d) *** ## Menus at a glance | Menu | What it does | App type | | - | - | - | | **Home** | Today's channel / meeting count and duration, with weekly, monthly, and yearly trends | All | | **Channel management** | Channel list, online users, assigned media node; open details to see users and call quality | Audio and video | | **Meeting management** | Meeting list (upcoming / in progress / ended), scheduled meetings, meeting details, and in-meeting controls | Meeting | | **Recording management** | Default recording layout, watermark, and window labels; recording file playback and download; voice recording | All | | **Device management** | Register SIP / H.323 endpoints, RTSP streams, and GB28181 cameras, and view their online status; see [Room Connector](https://docs.stmlink.com/en/product/device-access/overview.md) | All | | **Contacts management** | Departments and members, used for meeting invitations | Meeting | | **Video on demand** | Cloud media library, cloud editing, cloud transcoding, transcoding templates, and VOD nodes | All | | **Top-up management** | View this platform's platform code (provided when applying for a license), and allocate user concurrency, device concurrency, and validity period to apps | All | | **File licenses** | Import license files and view the total and remaining quota of each license | All | | **Device licenses** | Activation records and expiry dates of client devices | All | | **System management** | Console accounts, roles, and menu permissions | All | | **Operations management** | Client access addresses (network lines), media nodes, media gateways, MCU alarms, and operation logs | All | Menus are shown according to the account's role permissions. If you can't see a menu, ask your administrator to grant the permission. *** ## Meeting management and in-meeting controls You can control meetings in progress directly from the console: **mute all / unmute all, lock the meeting, start recording, invite members or devices, view meeting monitoring, and end the meeting**. Below that, you can view and export in-meeting members, members who have exited, members who haven't entered, sign-in records, and chat history. ![Meeting details](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/images/admin-meeting-detail.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=03c75f0ed6bc575ac87217b005906c89) *** ## Recording management Set the default video layout for cloud recording (auto grid, or a custom layout with specified members, up to 25 tiles), the recording watermark, and window labels; play back and download recordings under **Recording files**; and view per-speaker audio segments under **Voice recording**. ![Recording settings](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/images/admin-record.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=341ab40e5fe6cffe20da362741f8cf8d) *** ## Operations management **Media nodes**: each media forwarding node's online status, load level, CPU / memory, channel and user counts, network line, and historical load curve. For multi-node deployments, you also adjust the scheduling policy here. ![Media nodes](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/images/admin-sfu-node.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=9fb669e8cc5ec2f75795f4ff1415b631) **Media gateways**: the running status, task count, and load of gateways such as MCU, device gateway, voice recording, and speech recognition. ![Media gateways](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/images/admin-media-gw.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=7b312fb9d438301b2d5ca6e5773f3296) **System configuration → Network**: the access addresses each network line delivers to clients; see [Internal network and public internet](https://docs.stmlink.com/en/product/deploy/networks.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.