Who can use Chat
- Every member of the organisation the Chat deployment serves, in any role. Each Chat deployment serves exactly one organisation.
- Nobody else. An account from another organisation is refused at sign-in. There is no guest access and no Chat-only account.
- Nobody is an administrator inside Chat. Chat’s own admin powers — rewriting its endpoints and tool servers — are deployment-level, so no customer account is given them, whatever its role in the console.
Sign-in and sign-out
Chat has no password of its own. Sign in goes to the MITHUNAI sign-in page; see Sign in once. Log out in Chat ends your Chat session. Once single sign-out reaches your deployment, signing out anywhere else ends your Chat session the next time Chat renews the sign-in, within about fifteen minutes; until then, a Chat tab that is already open stays signed in. See How signing out works. When someone must lose access at once, tell your MITHUNAI contact.The two keys behind Chat
The knowledge key never reaches the model or the browser: it travels only between Chat’s server and
MITHUNAI.
To rotate the knowledge key, create a new Member key in the console, give it to whoever runs your
Chat deployment, and revoke the old one once they confirm Chat restarted on the new key. Revoking the
old key first switches the Knowledge tool off for everyone until the new one is in place.
Your brand in Chat
Chat takes its colours from your organisation’s branding when it starts. A colour change reaches Chat at its next restart, not at once. If the branding cannot be read when Chat starts, it opens in its own default colours rather than failing. Each person chooses light, dark or system mode, and Increase contrast, for themselves under Settings.What is switched off, and why
Chat is built on LibreChat, an open-source chat workspace, and runs with far fewer capabilities than it can. Each capability left out is something that could run code, browse, or call a third party that nobody reviewed. None of these is reachable unless the operator of your deployment sets it up deliberately.
These are on by default: saved prompts, bookmarks, temporary chats, side-by-side replies, shared
links inside your organisation, agents in Chat, skills and scheduled chats. An operator can switch
any of them off.
On the hosted service, MITHUNAI operates Chat and these settings are fixed. On a private-cloud or
on-premises deployment, the operator sets them; a capability whose service is missing is refused at
start-up rather than shown as a button that fails. Ask your MITHUNAI contact before relying on
anything in the first table.
Data and isolation
- One organisation per Chat. A Chat deployment reads one organisation’s knowledge, through a key that belongs to it. MITHUNAI decides the organisation from the key, never from anything Chat sends.
- Threads stay in that Chat’s own database, and each person’s threads are their own.
- Every model call goes through the Gateway, so Chat holds no provider credentials.
- MITHUNAI does not train models on your conversations. See Security.