The Lynkoria console
Roles, analytics, audit history and webhook monitoring in the admin console.
The console is where your team manages projects, environments, keys and team access, and watches usage, recordings, push delivery and attachment scanning. It is internal: there is no sign-up. A platform operator creates your account with pnpm admin:user create, and you sign in with email and password. Deployments may also put the console behind Cloudflare Access; then your Access identity must match your console account. See admin access and authentication.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including granting and removing console roles. |
| Admin | Manage projects, environments, keys and webhook retries. |
| Developer | View projects, key metadata, usage and operational data. |
| Auditor | View configuration, usage and the audit log. |
A role is granted organization-wide or for a single project, from Team & roles, which also shows each member's last activity in this organization (their latest audited action on its projects). It never shows sign-in details from other organizations. Removing a role takes effect on the next request. Sessions end after 30 idle minutes or 12 hours; disabling an account signs it out everywhere.
Calls and livestreams
Each project's Calls tab shows what is happening now and what happened before:
- Live state per environment, refreshed every 15 seconds while the tab is visible: active calls by type, connected participants, livestream audience (hosts and viewers together), possibly stale calls, and the concurrent-room quota as a meter (the same count the API uses to refuse new calls).
- Call list: active, ended or all calls, filtered by type, environment or a
productCallIdprefix, newest first. Filters and the open call are kept in the address bar. - Call detail: status, duration, participant sessions (product user and device, join time, time in call). Media, chat and recordings are never shown.
- Actions (owners and admins): End call disconnects everyone, stops new join tokens and sends your backend
call.endedwith reasonended_by_console. Remove participant disconnects one device; the user can rejoin if your backend issues a new token. Both are recorded in the audit log.
A call is possibly stale when it is active, nobody is connected and it started more than 10 minutes ago. The reconciler normally ends such calls within a minute or two; a growing number means LiveKit webhooks are not reaching the API.
Operations
Each project's Operations tab lists recent push deliveries (provider, status, attempts, last error), recordings (Egress status and files) and attachment scan verdicts (infected, rejected and failed scans, with the detected type). It shows identifiers and verdicts only, never file contents or message text.
Overview
The Overview page covers every project you can access:
- Right now: active calls, connected participants, livestream audience, possibly stale calls and dead-lettered webhook deliveries. It refreshes every 15 seconds while the tab is visible and pauses in background tabs.
- Last 30 days: calls created, participant minutes, messages sent and API requests (each with a daily sparkline), and the API error rate.
- Activity chart for one metric over the last 24 hours or 7 days (hourly buckets in your time zone) or 30 days (UTC days).
- Projects: status, live activity, 30-day usage and dead webhooks per project.
- Recent console activity for owners, admins and auditors.
Analytics
Analytics (all projects) and each project's Analytics tab show usage from the hourly and daily rollups (ADR 025):
| Control | Behavior |
|---|---|
| Range | Last 24 hours or 7 days (hourly buckets), 30 or 90 days, or a custom range of UTC dates up to 400 days (daily buckets). Hourly data is kept 35 days. |
| Time zone | Hourly labels in your time zone or UTC. Daily buckets are always UTC days. |
| Compare | Adds the previous period of the same length as dashed lines, and the change on each tile. |
| Scope | All projects or one project (on the Analytics page), and one environment. |
Charts start where data collection began: earlier buckets are shaded Not collected instead of drawn as zero (hourly collection starts when migration 0004 is applied). Every chart can switch to a table. The Analytics page also lists totals per project. Metrics are defined in the metrics catalog; figures are operational, not a billing ledger, and presence activity and bandwidth are not metered.
API keys
The API keys tab lists each key with its environment, scopes, last use and status. Select a key for its full details and change history. See projects and API keys.
Webhooks
The Webhooks tab shows each environment’s endpoint, signing-secret status and backlog (pending deliveries with the age of the oldest, and dead-lettered deliveries), plus the delivery history: pending, dead-lettered and delivered events with attempt counts and last errors, paged newest first. Payloads and secrets are never shown. Admins can retry dead-lettered deliveries. See webhooks.
Audit log
Every console change is recorded with actor, action, target, IP address, user agent, request ID and metadata, and so are sign-ins, failed sign-ins, sign-outs, ended sessions, usage exports and refused changes (console.denied, for example a developer trying to create a key). Credentials are never recorded. Entries are append-only: the database rejects any update or deletion, whoever asks.
Open a project’s Activity tab for its history, or Audit log for everything you can read. Filter by scope, action group (projects, environments, service keys, webhooks, roles, sign-ins and access, exports), actor email and date range; the filters are kept in the address bar so a filtered view can be shared. Select an event for its full details. Owners, admins and auditors can read the log.
Exports
Export CSV on a project's Analytics tab downloads daily usage for the selected range (up to 400 days). The file is built by the API, not the browser, contains only usage counts, and every export is recorded in the audit log (usage.exported). Any role that can read the project can export.
Your account
Account and sessions in the account menu lists the browsers signed in to your account (device, IP address, sign-in time, last activity) and lets you end any session other than the current one. It also shows your last 50 sign-ins, failed attempts and sign-outs. Password changes, recovery and disabling an account are done by a platform operator with the CLI.
Metric definitions
Every number the console shows has an info button with its definition, source, aggregation and delay, from the same catalog as the metrics catalog. Terms follow the glossary.
What the console does not do (yet)
| Capability | Why | Tracked as |
|---|---|---|
| Delete a project | Destructive; disable instead (reversible) | PD-3 in status |
| Create, disable or reset console accounts | Done by operators with pnpm admin:user | PD-1, PD-4 |
| Infrastructure and service health, other organizations' data | Needs a platform operator role | PD-1 |
| Latency, error rates by route, CPU, memory, realtime connections | Needs a monitoring backend | PD-5 |
| Users online | Presence has no per-environment counter | Metrics catalog |