Join us June 23 to see the ROI of switching to Tailscale.REGISTER ->

Aperture admin dashboard reference

Last validated:

Aperture by Tailscale is currently in beta.

Access the Aperture dashboard at /ui/ on your Aperture hostname (for example, http://<aperture-hostname>/ui/).

Every page described on this reference is visible only to users with the admin role. For non-admin users, the Security, Administration, and Reference sidebar groups do not appear, and the admin pages within Usage & Adoption do not appear in their navigation.

This page documents the admin-only dashboard pages. For the pages every user can access (the My Aperture group and the Usage Overview page), refer to the Aperture dashboard reference.

This topic is part of the Aperture reference documentation.

Usage & Adoption (admin)

The Usage Overview page in this group is visible to all users and is documented in the Aperture dashboard reference. The remaining pages below are admin-only.

User Activity

The User Activity page shows daily active user counts as a chart, with a grouping toggle (day, week, month, or 4-of-7 daily active users). It is filterable by date range.

Model Activity

The Model Activity page shows a stacked histogram by model, with a dimension toggle between tokens and cost. Below the chart, a sortable, paginated table lists each model with input, output, cached, and reasoning token counts, total tokens, request counts, average cost per million tokens, and a cost column.

Agent Activity

The Agent Activity page uses the same layout as Model Activity but groups activity by agent (user agent) instead of by model.

Chat Activity

The Chat Activity page is available to admins when either the chat_ui feature flag is enabled for the instance or chat is enabled for the viewing admin's account.

The Chat Activity page summarizes chat usage across several sections:

  • A chart that toggles between an activity view (user messages versus assistant turns) and an outcomes view (assistant turn stop reasons such as completed, error, canceled, refusal, truncated, context exceeded, and loop limit).
  • Stat cards for conversations created, active chat users, messages sent, and error rate, plus a turn breakdown.
  • A health section listing top error messages and per-model error stats.
  • A cost section with total tokens, estimated cost, cost per turn, and cost per conversation.
  • A files section with user upload counts and volume.
  • A per-user table with conversations, messages sent, assistant turns, errors, and last activity.

The User Search page is a form with a login-name input and an Open button. Submitting it opens that user's dashboard at /ui/dashboard/:loginName.

Quota Usage

The Quota Usage page shows quota balances and model coverage information for the instance's configured quota buckets.

Security

The Security group is visible only to admins.

Logs

The Logs page shows request history with session grouping. It provides the following views:

  • Sessions list: Shows aggregated metrics per session (total tokens, request count, and duration).
  • Session expansion: Select a session to show its individual requests.
  • Request detail: Select a request to show full capture data, including headers, request body, response body, and tool use details.
  • Filtering: Filter by date range, model, or user.

Session grouping helps you understand the context of conversations. A Claude Code session can show dozens of requests that together represent a single coding task.

Tool Use

The Tool Use page shows tool invocation patterns across sessions:

  • A histogram of tool invocations over time.
  • A data table of tool use with sorting and pagination.
  • Filtering by login name, model, user agent, tool name, starred status, and date range.

When an Oso integration is configured and enabled, an inline button links out to Oso for security alerts.

Audit Logs

The Audit Logs page displays a paginated table of audit events recorded by the Aperture instance.

  • Table columns: time, actor (the login name of the user who performed the action), action (color-coded by type), subject (the login name of the affected user), resource (type and ID), and access method (UI or API).
  • Tracked actions: data access events (captures, metrics, exports, session data), configuration changes, and quota operations (refills, balance changes, pausing).
  • Expandable detail rows: events with detail data display an expand chevron. Configuration change events show a unified diff view with syntax-highlighted additions and deletions. Other events show structured key-value metadata or preformatted text.
  • Filtering: combinable filter pills for six dimensions: date range (presets or custom picker), actor, action, subject, resource type, and access method. Filtering runs at the database level.
  • Pagination: server-side pagination with a default of 50 events per page.
  • Column visibility: a dropdown to show or hide individual columns.

Administration

The Administration group is visible only to admins and holds the configuration pages for the instance.

Providers

The Providers page is a visual editor for the LLM providers configured in your Aperture configuration, including their API keys.

Grants

The Grants page is a visual editor for access grants, which control which users and groups can reach which models, tools, and quotas.

Connectors

The admin Connectors page (/admin/connectors) is a visual editor for the connector servers available to your instance, which can expose MCP servers or generic APIs. This is distinct from the personal Connectors page in My Aperture, where individual users connect to those servers.

Hooks

The Hooks page is a visual editor for configuring request hooks that run against requests passing through Aperture. For details on hook events and configuration, refer to the hooks configuration reference.

Quota Configuration

The Quota Configuration page is a visual editor for quota bucket definitions and their grant assignments. It shows coverage hints indicating which buckets are covered by tailnet policy.

Data Export

The Data Export page configures the capture storage backend (local or S3) and the data retention policy. For a walkthrough, refer to Export usage data to S3.

Chat

The admin Chat page is available when the chat_ui feature flag is enabled for your Aperture instance.

The admin Chat page (/admin/chat) curates which models appear in the chat application's model picker, including their display names, ordering, and title or summarization roles. If the chat UI is disabled, the page shows an alert linking to the Feature Flags page. This is distinct from the external Chat application linked from My Aperture.

Feature Flags

The Feature Flags page enables or disables instance-level feature flags.

Configuration

The Configuration page is a raw HUJSON editor with syntax highlighting for editing the full Aperture configuration directly. Saving through this page applies the same validation as the API: warnings are treated as errors and the save is rejected until they are resolved.

Reference

The Reference group is visible only to admins.

Integrations

The Integrations page is available when the new_integrations_tab feature is enabled for your account.

The Integrations page (/admin/integrations) displays available partner integrations and custom webhook connections.

  • Category filters: chip buttons to filter integrations by category: Security, Monitoring, Compliance, Analytics, Developer, or All.
  • Integration cards: each card shows the integration name, description, logo, category badge, and configured or disabled status.
  • Detail overlay: selecting an integration opens a detail view with a full setup guide, deep link buttons, and enable or disable controls.

For setup instructions for individual integrations, refer to Integrate with external tools.

API Docs

The API Docs page is an interactive OpenAPI reference for the Aperture REST API.

  • Interactive documentation: browse endpoint descriptions, request and response schemas, and authentication requirements.
  • Try it: test API requests directly from the browser against the running Aperture instance.
  • Base URL: API requests use the base path /aperture on the Aperture node's tailnet address (for example, http://<aperture-hostname>/aperture).
  • Authentication: Tailscale identity authenticates all requests. No API keys are required.
  • Theme support: the reference viewer respects the dashboard's light and dark theme setting.