Enterprise Server

Administration pages

The pages for server admins: connecting code, reviewing what the team's assistants learn, and seeing who is connected and what it costs. Every write here is audited.

Repositories

Connect GitHub or Azure DevOps and choose which repositories this server indexes. The GitHub panel lists the App's installations — including ones made on GitHub's own settings page, registered here with one click — and the repositories each can reach; Azure DevOps lists the organization's projects. The server re-verifies a selection with the provider before it indexes it, records the repository's canonical remote so assistants in a checkout resolve to it, and queues a sync and index of the default branch.

Freshness is shown honestly — recently synced, stale, never synced, sync pending, failed, deselected — with a way to re-index or retry. Only pushes to the default branch queue new work. Set the App or the organization up first under Settings → GitHub App and Azure DevOps.

Memory review

Nothing an assistant or an import writes reaches other people's briefs until someone may approve it.

  • Memory — candidates from assistants' writes, repository imports and syncs, and knowledge uploaded here, each shown as it will be stored. Approve or reject; nobody reviews their own candidate unless the server is set to allow it, and then it is audited.
  • Knowledge — the catalog's queue: proposals to replace an approved description, shown beside the current one; unreviewed descriptions the LLM or assistants wrote, beside the extracted one; and stale approved ones written before the code changed. Accept, edit and accept, reject, confirm or reset each.

Team

Everyone with a membership in the organization, and each of their connections: a CLI on a device, or a browser on this console. For each: the device name, operating system, CLI version, AI client, and when it was last seen — counts only, never content.

Team: who is connected, from which devices, and how much each AI provider is used (illustration).
  • Usage: tool calls per day stacked by AI provider, CLI versions, and a per-member table, over 7, 30 or 90 days.
  • Disconnect refuses one connection from now on and asks Knwlge Global to revoke its refresh token; Sign out everywhere does it for all of a person's connections. Neither is a ban — the person can sign in again. To remove someone, remove them from the project in the Knwlge app.

Prompts

Two tabs, for what prompting cost and what Knwlge gave back.

Prompts → Dashboard over 30 days, charting tokens used by model (illustration).
  • Dashboard — over 7, 30 or 90 days: prompts with their sessions and people, tokens used, tokens saved and Knwlge calls. The figure you choose is charted per day (tokens stacked by model). Below: the models and AI clients, then everyone active, with a link to their prompts. Tokens used are what the AI client's own transcript reports — Claude Code today; other clients show not reported, never zero.
  • Prompts — what people typed while connected to this server, newest first, as capture stored it: secrets removed and personal data masked. Filter by person, repository, client, day or text. A session opens its timeline: prompts, and each tool use, edit, shell command and MCP call by kind, tool, files and exit status — never the command, the tool's output or the assistant's reply. Knwlge's own calls stand out in the Knwlge colour.

Activity

The sanitized events this server observed — context requests, corrections, indexing, activation and security events — with a filter by category. Filtering changes only the view, never the evidence.

Alerts

Operational issues and audit warnings: failed provider tests, sync jobs that need a retry, deletes that did not complete. Acknowledge an alert, or — when KNWLGE_ALERT_WEBHOOK_URL is set — send it to your operations endpoint, signed. Both are audited.

Audit

The admin audit trail: provider key and configuration changes, sign-in settings, updates, reviews, prompt views, disconnections — filtered by action, severity, person and time, on the server. Export it as NDJSON for your SIEM; the export is audited too. Events are kept for KNWLGE_AUDIT_RETENTION_DAYS (365 by default) and can be shipped continuously (Audit, alerts and retention).