The Monitoring views are admin-only. Non-admin users are redirected away from protected routes.
Usage analytics
In the Usage & Costs section, you can monitor:- Number of message sent by users to the chat
- Total tokens consumed
- Total cost of tokens consumed
- Channel usage split across Web, Slack, and Microsoft Teams
Feedbacks monitoring
In this section, you can see all postive and negative feedbacks sent by users in message threads. The Feedbacks table shows:- Vote - Thumbs up (👍) for positive feedback or thumbs down (👎) for negative feedback
- User - Who provided the feedback
- Message - The agent’s response that was rated (truncated preview)
- Reason - User’s explanation for their feedback (if provided)
- Date - When the feedback was given
Chats replay
In this section, admins can inspect historical chats at the project level and replay messages for debugging and quality checks. The Chats Replay view includes:- Project-wide chat table - Browse chats in the current project
- Filters - Filter by column visibility, date, users, role, and tool state
- Replay panel - Navigate previous and next feedbacks or tool errors from a selected chat
Asset analytics
Every chat and story keeps a record of how it has been used, so you can see whether a report is actually read and by whom. Open it from:- A chat: the Analytics icon in the chat header.
- A story: Analytics in the story header menu.
Repeat views by the same person on the same asset are collapsed inside a two-minute window, so refreshing a page does not inflate the count. Views coming from an embedded story, where there is no signed-in user, are grouped under anonymous.
Asset analytics are visible to the owner of the chat or story, and to admins for any asset in the project.
v_analytics_event view in admin mode (see below), which is the better route for project-wide questions such as “what are the most viewed stories this month?”.
Chat with your nao data (admin mode)
Admin mode lets you ask questions about how your nao project is being used, in natural language, instead of reading the usage dashboards manually. In this mode the agent answers by running read-only SQL over nao’s own application data. Turn it on from the chat, in two ways:- The Chat with nao data entry in the settings sidebar.
- The Admin mode toggle in the chat input menu. When it’s on, the chat input shows an amber border and an Admin Mode badge so it’s clear you’re querying internal data.
v_messages- full message history: user prompts, assistant answers, tool calls and errors, feedback votes and explanations, the model used, and the source (Web, Slack, Teams, etc.). The richest view for adoption, tool errors, and downvotes.v_analytics_event- asset engagement events (page views, downloads, forks, favorites, refreshes, view duration) for chats and stories.v_llm_inference- one row per LLM call, with type and token usage.v_mcp_call_log- MCP tool calls.v_memories- saved memories.v_project- project metadata.
SELECT / WITH only) and cannot touch anything outside the allowlisted views.
Logs
Navigate to Settings -> Logs to view the agent’s server-side logs in a terminal-style viewer. Features:- Date range filter - filter by preset ranges (last 15 minutes, 1 hour, 24 hours, 7 days) or a custom date and time range. Defaults to the last hour.
- Load older logs - scroll to the top of the log viewer or click the header to load older entries. Pagination is cursor-based.
- Expandable rows - click a log row to expand the full message text and see the
contextJSON payload when present. Truncated rows show a chevron indicator.
Admin Setup
Configure users, authentication, and integrations
Context Engineering Playbook
Learn how to systematically improve answer quality