Skip to main content
Version: v2026.0.0

Admin panel overview

The admin panel is the <admin-element> web component embedded in the Uxopian AI interface. It provides a UI for managing prompts, LLM providers, MCP servers, usage profiles, scripts, code modules, agents and plans, for browsing users and conversations, and for viewing usage statistics. Since 2026.0.0 it has a redesigned look, shared with the chat and Quick Prompt components. All operations are performed per-tenant via the Admin REST API.

Accessing the admin panel​

The admin element is loaded from the web component bundles served by uxopian-ai. The admin script and style are available at:

AssetEndpoint
Admin JavaScript/api/web-components/admin/script
Admin CSS/api/web-components/admin/style

To embed the admin panel:

<link rel="stylesheet" href="https://your-gateway/api/web-components/admin/style" />
<script src="https://your-gateway/api/web-components/admin/script"></script>

The <admin-element> custom element accepts the following attributes:

AttributeTypeDescription
basePathstringBase path for React Router routing inside the element
apiEndpointstringBase URL of the gateway/DNS host serving uxopian-ai, without the /api/v1 suffix (e.g., https://your-gateway). The component appends /api/v1 itself.
swaggerEndpointstringOptional address of the Swagger UI the Swagger UI link opens. Resolution order: swaggerEndpoint, then apiEndpoint, then the address the panel is served at. Set it to aim the link at the gateway Ingress
getAccessTokenfunctionOptional callback function that returns the current access token

Add the element to the page after loading the script:

<admin-element apiendpoint="https://your-gateway"></admin-element>

In the default Docker Compose quickstart, the admin UI is accessible via the gateway at http://localhost:8085.

The navigation is a collapsible rail on the left, always visible: the toggle at its bottom (or the [ key) switches between icons only and icons with labels, and group titles show only when it is expanded. The theme toggle is in the same place. Each page owns its title and subtitle, and a back link (a breadcrumb trail only from the third level) returns to the list you came from, scrolled where you left it.

The sections of the rail:

GroupEntryRouteDescription
OverviewDashboard/Summary statistics
AIPrompts/prompts, /prompts/:idPrompts: versions, model, answer format and Quick Prompt display settings
AILLM providers/llm-providers, /llm-providers/:idProvider configurations: credentials, endpoint, models
AIMCP servers/mcp-servers, /mcp-servers/:idMCP servers
AIUsage profiles/usage-profiles, /usage-profiles/:idUsage profiles (called Applications before 2026.0.0): defaults and permissions per usage surface
AIScripts/scripts, /scripts/:idAdmin-managed scripts
AICode modules/code-modules, /code-modules/:idJavaScript modules and tools run in the code sandbox
AgentsAgents/agents, /agents/:idAgent configurations used by plans: objective prompt, success criteria, permissions
AgentsPlans/plans, /plans/:idPlans: flow editor and runs
ReviewReview tasks/viewerHuman review screen; opens in a new tab
AnalyticsUsers/users, /users/:idUsers and their conversations
AnalyticsStatistics/statisticsUsage charts: time series, LLM distribution, feature adoption
ResourcesDocumentation, Swagger UIexternalOpens the documentation site and the API explorer

Creation pages live under /<section>/new/edit.

Working with lists and detail pages​

All list pages work the same way:

  • Server-side pagination, search, filters and sorting. Only one page of entries is fetched at a time, so large collections stay reachable (the Applications, Agents and Plans lists used to stop at 25 entries). The matching REST endpoints answer a page { collection, total, facets } — see the REST API summary.
  • Columns can be resized by dragging, hidden and reordered; the layout is remembered. An empty list keeps its table header.
  • A single click opens a quick view of the entity, the up and down arrow keys walk through the list, and a double-click opens the entity for editing (on the Users list it opens the user detail).
  • An "Used by" column names the entities that reference each entry; an unused one shows a dash.
  • Names are checked while you type. Every entity is identified by its name alone, and the creation form reports a name that is already taken before you save (GET .../availability?id=).

Detail pages share one layout: a title with badges, an action bar with the primary action, secondary actions and a "..." menu (for example Reset, Discard draft, Delete), then foldable cards that show a one-line summary once filled in. The editor warns before you leave a page with unsaved changes, and deleting an entity you just edited does not ask you to save first.

The admin console is served with a strict Content-Security-Policy (no inline script, no eval) and cannot be framed: embed it through the <admin-element> web component, not an <iframe>.

Authorization​

In the default gateway configuration, the admin API routes (/api/v1/admin/**) are marked public. For production deployments, restrict them by adding a roles rule:

app:
routes:
- id: uxopian-ai
security:
- path: /api/v1/admin/**
roles: ["ADMIN"]

The roles field requires that the authenticated user's role list (from X-User-Roles) includes the specified role.