---
title: "Protect Channel Credentials"
description: "Treat access tokens and channel secrets like passwords."
category: "Security"
canonical: "https://www.proxyai.app/help/security/protect-channel-credentials"
---

> For the complete documentation index, see [llms.txt](https://www.proxyai.app/llms.txt). Request public content pages with `Accept: text/markdown`.

# Protect Channel Credentials

Channels setup forms require credentials that can control your messaging channels. Copy them only from each provider's official console, enter them directly in your chatbot configuration, and never publish them in help requests, screenshots, source control, or client-side code.

If a credential is exposed, rotate it with the channel provider, update ProxyAI, save the new value, and check webhook or connection status again.

### Prepare a safe support example

When a connection fails, record the channel name, the selected chatbot, the time of the failure and the visible error message. Describe which step failed without including the credential itself. A screenshot of a settings form should have tokens, secrets and unrelated customer information removed before you share it.

Use the provider's own console to distinguish a copied value from a revoked or replaced value. Follow the matching [channel guide](/help/integrations) when updating the connection, because different channels use different credentials and permission flows. A Telegram bot token is not interchangeable with a LINE channel secret or a Meta app credential.

If you suspect exposure, replace the credential at its source and update the stored connection rather than merely deleting the screenshot where it appeared. Then test an incoming message and check that you are editing the intended chatbot.

Keep a record of which provider account owns each connection. That helps the right administrator investigate a permission change later without sharing secrets between team members or publishing them in documentation.
