Authenticated chat uses a signing key, shared between Assembled and your backend, to confirm who a logged-in user is. Use these steps to generate a new key in Assembled and install it where your backend signs chat tokens (JWTs).
If you're here because of the November 13, 2026 security incident: Assembled has already rotated authenticated chat keys, so the key shown in Assembled may no longer match your backend. Chat keeps working, but it won't recognize logged-in users until your backend signs with a new key. Generate a new key to see its full value. For more about the incident, see November 13, 2026 security incident.
Who does this
- Someone in Assembled who can edit your chat profile setup.
- An engineer on your team who can update the backend that signs chat tokens.
Before you start
- Make sure the engineer who manages your backend is available to install the new key right after you generate it.
- Agree on a secure way to pass the key to them. Don't send it by email, chat, or in a ticket.
Steps
- In Assembled, go to AI support > Chat agent > Chat profile > Setup. Under User data authentication, generate a new key.
- Have your engineering team securely install the new key on the backend where your chat tokens are signed. Keep it on the server only. Never put it in browser code.
- Test chat as a logged-in user and check that their details, any personalization, and handoff fields come through as expected.
How to confirm it's working
- A chat started by a logged-in user is recognized, and the expected user details reach chat, workflows, and handoffs.
When you'll see data
The new key takes effect as soon as your backend starts signing tokens with it.
Restoring missed data
There's no data to backfill. Chat kept working while the keys didn't match; it just treated logged-in users as anonymous.
Things to watch for
- Generate a new key to see it. The key shown may not match your backend, and generating a new one shows its full value.
- Update every environment. If more than one backend or environment signs chat tokens, install the new key in each.
- Keep the key private. Install it only on your server. Don't paste it into tickets, email, chat, or browser code.
- Test as a logged-in user. Anonymous chats keep working either way, so test with a signed-in account.
Need help?
If logged-in users still aren't recognized after you update your backend, contact our Support team. Please don't send the key itself by email or chat.