Each tool is one thing Claude can do (read = safe lookup, write = changes data). Most are added for you - from a template, or by importing a system's API spec on its connection. Building one by hand is an advanced fallback.

Usage, users, and errors at a glance, so you can see what's working without reading the log line by line. The raw audit log is still available under Audit.

"Unused" only means unused within the audit log's retention window (90 days) — usage older than that has already aged out and cannot be seen here.

Daily call/user/fault counts, kept in their own small record outside the audit log so they outlast its retention window.

A group is a named basket of tools, skills, and actions you hand to people and API keys. Click a row to see everything it grants, who has it, and manage membership. To build a variant of an existing group, open it and use Duplicate - no re-picking from scratch.

Staff appear here automatically when they connect Claude. Tick a group in a person's drawer to grant access — it saves instantly, no reconnect, and the confirmation reports exactly what changed and what that person can now reach.

Helix is a shared knowledge pool every connected worker can search, read, and contribute to from Claude - a place to capture things people learn. Entries publish immediately; you can edit or remove any of them here. A source connects a document URL (like an llms.txt) and keeps its contents here as a synced entry you refresh on demand. Personal notes belong in each worker's private Memory instead - if one was filed here by mistake, Move to memory hands it back to its author privately.

Memory is each worker's private note store in Claude - preferences, ongoing work, personal reminders - tied to their account. Content is visible only to its owner, never here: this page shows per-person counts so you can see the feature is being used, nothing more. Shared, company-wide notes live in Knowledge.

No one has saved a private note yet. Workers save them from Claude - "remember that I..." - with the memory_add tool.

Skills are installable bundles (a SKILL.md plus optional files) that workers add to their own Claude. Workers can contribute from Claude; submissions wait here for your approval. Access is granted per group (on the Groups tab), and a skill installs to its scope - project, personal, terminal, or Claude Desktop.

The backlog of bugs, feedback, access requests, and feature/change requests about Helix itself, filed by workers from inside Claude - click a row to read a request, add notes, and resolve or decline it.

Accepted work, kept separate from the open request queue so "yes, someday" doesn't clutter what's actively being triaged. Add an item two ways: promote a request from its detail page (Add to Roadmap), or author a net-new item below. Work an item in place: move its status (Planned → In progress → Done) and keep notes on its thread - marking it Done posts the outcome back on the request it came from, so the original filer sees what shipped. Removing an item deletes it; it does not reopen any request it came from.

Actions are specific commands that run on the Helix server host itself - for wrapping tools that have no API, or triggering scripts you deploy alongside the server. They are defined in code (src/actions.ts) and shipped with the server, not created here; this page lists the catalog. Grant an action to a group on the Groups tab, exactly like a tool. Each accepts only typed, validated arguments and never runs through a shell. Turn actions off to remove every one from Claude and the REST API at once.

Web apps that staff have had Claude build for them - dashboards and mini-pages hosted on Helix at a private URL. Each reads company data with its owner's access through a read-only API key. An app is created, edited, and deleted by its owner from their My apps page; here you can review every app, archive one (it stops serving but keeps everything, restorable any time), and permanently delete an archived app.

API keys let a script, cron job, or other non-MCP system reach the library over a plain REST API (/library/*, described by /openapi.json). Each key carries a scope (skills, knowledge, tools, audit, actions, or all) and an access level (read-only or read & write). The secret is shown once at creation - store it safely; revoke any key here to disable it immediately.

An unattended TV or kiosk display, paired to show exactly one app - no sign-in required once paired (#118). Add a device to get a 5-digit code, then on the TV go to /tv and enter it. Whoever's there then picks which app the display shows - that's permanent for this device; change it here if it needs to switch.