#why agent widgets can only be enabled for agents with authentication disabled?
1 messages · Page 1 of 1 (latest)
AI-generated Answer for kishore_vb
Because the embed widget is a client‑side component that connects directly from the browser to the conversation WebSocket, it currently doesn’t support authenticated (non‑public) agents. The official docs state: “Widgets currently require public agents with authentication disabled.” For security, you should restrict access using domain allowlists in the agent’s Security tab. If you need authentication, use the SDK or WebSocket with signed URLs instead of the widget. (elevenlabs.io)
how to utilize the voice switch feature for agents