Skip to main content
Feature

Ask the whole company's knowledge one question

The HR policy is in one project, the product docs in another and last year's tickets in a third. Team chat searches all of them at once and tells you which document - and which project - every sentence came from.

  • Every project, or just one
  • Private history per person
  • Every citation names its project

What is team chat in SupaCortex?

Team chat is a chat page for the people who work in your SupaCortex workspace. A signed-in user asks a question in plain language; SupaCortex searches every active project in the workspace - or one project the user picks - and writes an answer only from the passages it found, with numbered citations naming the document, the section and the project. Each person has a private history of conversations to reopen, continue, rename or delete, and rates answers with a thumbs up or down.

  • Open to every role, Viewer and up - no separate licence.
  • Searches all active projects, or one project chosen per conversation.
  • Citations show document, section, passage, project and the source page link.
  • Says it could not find an answer rather than guessing.
  • Follow-up questions keep the context of the last few you asked.
  • Conversations are personal: another user's chat simply does not exist for you.
What it looks like

One answer, three projects, every source named

A question about travel claims touches the HR handbook, the finance process and an IT runbook. Nobody has to know where each one lives.

While the answer is prepared you see where it has got to - searching, writing, checking - and then the whole answer at once, with its citations already checked.

acme.supacortex.com/chat
How do I claim a client visit taxi fare, and which laptop VPN do I use there?

Submit the fare in the expense tool within 30 days with the receipt attached 1; trips over ₹2,000 need your manager's approval first 2.

On client networks use the Always-On VPN profile, not the split-tunnel one 3.

  • 1 Travel & Expenses Policy · 4.2 Local travel · HR Policies
  • 2 Approval Matrix · Expenses · Finance
  • 3 Remote Access Runbook · Client sites · IT Runbooks

Illustration. Documents and projects are examples.

In detail

Built like the assistant people already use, kept to your documents

A history that belongs to you

Team chat works the way people expect a chat assistant to work - only the knowledge is your company's.

  • New chat, then a history grouped Today, Previous 7 days and Older.
  • The first question names the conversation; rename it whenever you like.
  • Reopen and continue any chat - follow-ups are read with your last few questions.
  • Delete a chat and it is gone from your history.
  • Copy an answer, or rate it up or down, from the message itself.

Across projects, or inside one

Projects keep knowledge tidy for the widget and the API. Team chat lets staff ignore the filing system when they need to.

  • Every active project is searched unless you narrow the chat to one.
  • The scope is saved on the conversation, so reopening it keeps the same focus.
  • With several projects in scope, each passage is labelled with its project before the answer is written.
  • A deleted project widens its chats back to every project instead of breaking them.

Deactivating a project removes it from team chat straight away; reactivating it brings it back.

The same checks as every other answer

Team chat runs through the same answer engine as the widget, the API and the playground - nothing is looser because the audience is internal.

  • Hybrid search, with official documents outranking past tickets.
  • A confidence gate: no relevant passage means "I couldn't find this", not a guess.
  • Citations are checked against the passages; an answer that fails is written once more, then withheld.
  • The model runs on infrastructure we operate - your documents are not sent to a third-party AI API.
Frequently asked

Questions people ask before they start

Everyone with a sign-in to your SupaCortex workspace, from the Viewer role up. Website visitors and app users never see it - they use the chat widget, which answers from one project only. Team chat is the first item in the menu and the page people land on after signing in.

No. A conversation belongs to the person who started it. Nobody else - an Admin included - can open it, and team chats never appear in a project's Conversations tab. Thumbs-down ratings do reach the Insights page so the docs team can fix the gap, but without naming the person or the conversation.

By default a chat searches every active project in the workspace. A picker in the message box narrows it to one project and widens it again, and the choice is saved with the conversation. Every citation names the project its source came from, so an answer drawn from two projects says so.

Team chat covers every active project for everyone who can sign in. It does not copy file-by-file sharing from Google Drive or SharePoint, so material only a few people should read does not belong in the workspace. Deactivating a project takes it out of team chat at once.

No - team chat answers from your knowledge only. Live lookups and actions, such as an order status or raising a request, run in the chat widget and the chat API through a project's connector, where the person asking is verified.

Each answer uses 1 AI credit from the workspace's monthly allowance, the same as any other answer. If the model or search is unavailable, nothing is saved and the question stays in the box with a Retry.

Ask your own policies the question everyone emails HR about.

Book a 30-minute demo on your own documents. We set up a 14-day trial workspace for you - no credit card, no setup fee.

Questions first? Email info@greatdevelopers.com or call +91 8585953085.

Still curious? Ask your favorite AI about SupaCortex.