The **internal widget** is the same type of chat window as the public web widget (Manual 06), but configured so that **only your team** can enter — never a customer or an anonymous visitor. Instead of replying instantly to whoever opens the chat, the first screen asks you to **identify yourself** with your Platform account's email and password, plus a two-factor verification code. Once inside, you talk to the assistant **with your own role** — just as if you'd logged into the web Platform. Designed for a team that wants a quick, familiar chat channel to ask the assistant something from an internal page (an intranet, your own dashboard…), without opening the full Platform. > **Note — Don't confuse it with the public widget or with "Channel-linked access"** > > The **public** widget (Manual 06) is your assistant's face toward your customers — anyone can write to it > without identifying themselves. The **internal** widget in this manual is its opposite: nobody without a > Platform account can get past the identification screen. And it's different from "Channel-linked access" > (Manual 51): there you link your **personal** WhatsApp or Telegram with two-factor verification inside > the WhatsApp/Telegram chat itself; here you identify yourself with **email and password**, inside a > widget window. **AI disclosure:** on the identification screens (section 4) the header only shows "Internal assistant" — there's no conversation with the assistant yet, just the process of entering. As soon as you identify yourself, the header switches to showing, and keeps showing throughout the conversation, "Internal AI assistant · replies instantly" — the same transparency the law requires for any conversational assistant, even when it's your own team talking to it.