Skip to main content
How workspace admins find, use, and manage AI Workspace Co-Admin in the Vendschat dashboard.

How to open Co-Admin

Primary navigation

  1. Sign in to Vendschat.
  2. Ensure the correct workspace is active (workspace switcher is in Settings, not the main header).
  3. In the left sidebar, click AI Workspace Co-Admin.
  4. URL: /co-admin.
The nav item uses the workspace agent icon and shows the label AI Workspace Co-Admin. It is selected when the path starts with /co-admin.

Access control

  • /co-admin is an always accessible route — available even when a member’s role limits them to Chat only.
  • /agent is also listed as always accessible (legacy or alternate path; primary product surface is /co-admin).
  • Co-Admin still only returns data for the workspace tied to the current session.

When Co-Admin is unavailable

If the server returns 503 with “Co-Admin is not configured”, the deployment is missing OPENROUTER_API_KEY. This is an environment configuration issue — not something end users fix in Settings.

Page layout

The Co-Admin page is a full-height split view:
Hidden on small screens (mobile:hidden). Contains: Date groups for unpinned chats: Today, Yesterday, Previous 7 days, then Mon DD style dates.

Main chat area

Composer behavior

  • Multi-line textarea; Enter sends, Shift+Enter new line.
  • Send disabled while status is streaming or submitted.
  • Auto-focus returns to composer after a reply finishes.
  • Variant centered on empty state; docked when messages exist.

Chat history (server-backed)

Co-Admin conversations are not ephemeral browser-only storage. Prefetch: hovering a chat row may prefetch messages for faster switching.

Workspace scoping

Every API call includes the active workspaceId from the user session.
  • Switching workspace in Settings changes which live data Co-Admin tools return.
  • Chat history is separate per workspace — switching workspace shows a different sidebar history.
  • If workspaceId is missing from the chat request, the agent API returns 400 (“workspaceId is required for Co-Admin tools”).
Training note for Co-Admin: When users ask “my channels” or “our inbox”, always interpret as current workspace unless they name another workspace (which Co-Admin cannot access).

How replies render

Markdown

Standard markdown for headings, lists, bold, links.

Charts (required format)

When the assistant presents a chart (trends, comparisons, distributions), it must use a fenced chart block with JSON — not Mermaid xychart-beta, not a markdown table labeled as a chart. Supported type values: line, bar, area, combo, scatter, pie. Example bar chart:
The frontend parses these blocks and renders interactive charts in the message stream.

Tables

Markdown tables are for tabular data only when the user asks for a table — not as a substitute for charts.

Agent turn limits

  • Maximum 6 tool-call steps per user message (stopWhen: stepCountIs(6)).
  • Complex questions may combine overview + doc search + analytics within that budget.
  • If a question needs more, Co-Admin should answer in parts or ask the user to narrow the scope.

Mobile experience

The history sidebar is hidden on mobile. Users on phones still get the main chat and composer but manage history with reduced visibility — they may need desktop for pin/rename/delete unless a mobile history pattern is added later.

Co-Admin vs navigating the dashboard yourself

Co-Admin does not replace deep configuration UIs — it orients users and surfaces summaries faster.

Common UI troubleshooting

More Q&A: Limitations & FAQ.