The console was reorganised in October 2026. If you knew it as Knowledge, Ask, Assistants and
Operations, the table at the end of this tour says where each of those went. Old links and
bookmarks still open the right screen.
Signing in and the sidebar
Sign in with your email address and password. If you have forgotten your password, choose Forgot password? on the sign-in screen to get a reset link by email; see Password reset. If you were invited, open the link in the invitation email first and choose your password there; see Invitations. The sidebar is the same on every screen:- At the top, the logo and a search box. Search, or Ctrl+K (⌘+K on a Mac), jumps to any screen or Settings section.
- In the middle, the navigation: one row per screen under the headings Configure, Deploy, Analyze, Visibility and Workspace. Hover over a row to see what the screen is for. Below it are the links to the other surfaces.
- At the foot, Documentation, which opens this site in a new tab, and your account: your name and email address, and the Sign out button.
Dashboard
The first screen after you sign in. Until an assistant can answer, it shows a six-step setup guide: connect your knowledge, wait for the first sync, point an assistant at it, ask a question, put it on your website, and invite your team. Each step is ticked off as you complete it. Once an assistant can answer, the Dashboard shows, in this order:- The headline figures of the usage report: questions, conversations, grounded answers and declined answers, with the window beside its title. A rate with nothing to measure shows a dash.
- Sources: how many you have and how many need attention. Selecting it opens Sources.
- Coverage gaps: how many questions were declined or rated unhelpful in the last 30 days. Selecting it opens Coverage gaps. Owners and Administrators only.
- Answers this month: how much of your organisation’s monthly answer allowance is used, for example “850 of 1,000 answers used this month”, with a warning when it is nearly used and a notice when your assistants have stopped answering. Owners, Administrators and Editors. See Usage and limits.
- What to do next, such as putting the assistant on your website.
- The rest of the usage report: charts, failures, and a breakdown by model and channel, filterable to one assistant, for the last 7, 30 or 90 days.
Configure
Sources
Connect and maintain the content your assistants answer from.- Connect source opens a dialog with thirteen choices under four headings. Websites and files: Website, Sitemap, File upload, OpenAPI schema and Custom answers. Knowledge bases: Zendesk Help Center, Confluence and Notion. Issues and support: Jira, Jira Service Management and Zendesk tickets. Community: Discourse forum and GitHub, which reads a repository’s files, issues, pull requests or discussions, public or private. Confluence, Notion, Jira, Jira Service Management, Zendesk tickets and a private repository add a connection step, where you choose a saved connection or save a new one. The first time, the console creates a collection for you, and ingestion starts on save.
- Each source shows its ingestion status as the job runs. Its menu has Edit, Rename, Pause or Resume, Re-sync to ingest changes and Remove to delete it. Saving an edit does not read the source; the console offers Sync now as a separate step.
- The Ingestion tab lists recent ingestion jobs and their outcomes, with a running job’s progress and the ability to cancel.
Customizations
Create an assistant with New assistant, then set its name, the collections it answers from (Knowledge), its model and its guidance. A collection embedded with a different model from the ones already chosen is shown disabled, with the reason. Below the list, Assistant holds the name, model and guidance of the assistant the console itself answers with. See Configure an assistant and Models and providers.Deploy
Playground
Question an assistant the way your users will.- Answers stream in as they are written, with numbered citations that link to the passage behind each claim.
- When the content does not support an answer, the assistant says so, and the reply is shown as an abstention rather than an error.
- Under an answer you can Copy answer, rate it Helpful or Not helpful with an optional note, and pick one of up to three suggested follow-up questions.
- Your conversations are kept in a list, so you can return to them.
Integrations
One card for each way to reach your assistants from outside the console.
See Website widget, MCP server and HTTP API.
API keys
Create, list and revoke API keys. A new key’s secret is shown once. See API keys.Analyze
Conversations
What people asked and what the assistant answered, with the sources each answer cited. Owners and Administrators see every conversation in the organisation, whether it was held in the Playground, through the widget or over the API; everyone else finds their own in the Playground. The list shows each conversation’s title, message count and last activity, and it never shows who asked. Reading a conversation you did not take part in is recorded in the audit trail. It is read-only: to continue a conversation, use the Playground. See Conversations.Coverage gaps
Questions your assistants declined, and answers someone rated unhelpful, for the last 7, 30 or 90 days. Owners and Administrators only. Group similar questions, on by default, collects questions that mean the same thing into one row, and says so when it could group only by wording. It is in beta. A declined question is usually a gap in the content, and the fix is a source rather than a setting. See Coverage gaps.Top questions
What people asked your assistants most in the last 7, 30 or 90 days, answered or not, with questions that mean the same thing counted together and a CSV export. It never shows who asked: a question is listed only once three different people have asked it, and the rest are counted together. Owners and Administrators only; in beta. See Top questions.Source analytics
Which of your sources the answers cite, and which documents in them, for the last 7, 30 or 90 days, with a CSV export. Owners, Administrators and Editors. See Source analytics.Workspace
Settings
- Profile, Appearance and Keyboard shortcuts: your own account, the light or dark theme, and the keys that move you around the console.
- Members: the people in your organisation and the role each holds. Owners and Administrators invite someone by email, re-send or revoke a pending invitation, change a member’s role and remove a member. See Members and Invitations.
- Connections: the tokens your organisation saved for GitHub, Atlassian (Confluence, Jira and Jira Service Management), Notion and Zendesk, with Replace token and Delete. See Saved connections.
- Branding: product name, logos, colours and links, a terms link that appears in the console footer beside the privacy link, and two switches: whether the console footer shows a “Powered by MITHUNAI” line, and whether the widget shows your brand mark.
- Support access: whether MITHUNAI support may open a read-only session, who is in one now with End session on each, and what they read. See Support access.
- Deployment map: your assistants, the knowledge they answer from, and the keys and embeds that reach them.
Other surfaces
At the foot of the sidebar, More in MITHUNAI opens a menu of the other surfaces your deployment runs, such as Chat, Agents, AI employees and the AI Gateway. Each opens at its own address. Chat signs you in with the same account; Agents and the Gateway stand differently, and Agents is in beta, with access on request. See Other surfaces.If you are platform staff
MITHUNAI support staff and platform administrators see one extra group in the sidebar, Staff, holding Support and Model Gateway. Each is shown only to an account that holds that authority, and each is checked again on the server for every request. Customers never see either. See The staff entrance.Done with the API, not the console
- Creating a collection before connecting a source, and renaming or archiving one.
- Anything a script or pipeline should do repeatedly, such as re-syncing after a docs release: see Command line.
Where the earlier sections went
The sidebar itself was redrawn later in October 2026: one line per screen, with the description in a tooltip, the search box at the top, and Documentation and your account at the foot. No screen moved.