Documentation
What Jaha will and won’t say
An AI that speaks in meetings needs judgment as well as knowledge. Before Jaha says a word, it asks two separate questions: who is listening, and who asked. This page explains both, and what happens when the answer is “no”.
Two separate questions
Most tools treat meeting privacy as a single setting. Jaha treats it as two, because different people are involved: the AUDIENCE is everyone who will hear the answer, and the ASKER is the one person who asked for it. A colleague who may hear an answer isn't automatically allowed to call on the document behind it. And a client meeting can be safe for one question and wrong for the next.
Who is listening: discretion
Every meeting has a discretion policy: open, guarded or private. The host sets it, or it's chosen automatically from who is in the room. Every source has a sharing class: for the room, internal or restricted. When guests are present, Jaha stops saying internal material out loud. Restricted material is never spoken.
Some answers aren't refused but redirected: a private whisper gives the answer to the person allowed to have it, instead of announcing it to the room.
Who asked: answer scopes
Every document and connector also has an answer scope, which sets who can draw on it at all: anyone in the meeting, your organization, the owner’s team, or only the owner. “Only answer from my document when I ask” is a rule Jaha applies live to each spoken question.
“Team” has a precise meaning: the owner, their manager, their direct reports, and anyone who shares a team with them in your directory. It comes from the same org data the rest of the product uses.
How Jaha knows who spoke
In a Teams call, Jaha knows who spoke through Microsoft’s own identity, the same Azure AD identity your directory uses. Chat questions carry it too. Only when no identity is available does Jaha fall back to an exact, unique name match in the directory. If two people share the name, it matches neither.
When it says no
A refusal never gives away what it's holding back. In the room, Jaha says it has nothing it can share. It doesn't name the document it's protecting or hint at the answer, and it still answers from any sources the person asking is allowed to use.
The audit trail
Everything held back is recorded with its reason (which source, which rule, who asked) and shown to the host in the meeting’s discretion panel. Scope changes, ownership claims and deliveries all go into the audit log. A filter that works silently looks exactly like a broken product, so Jaha’s guardrails always leave a record.
Underneath all of this, every organization is isolated, sessions are hashed, retention can be set per plan, and consent can be revoked in your Microsoft admin center at any time.