Skip to main content
Settings › Chat Integrations lists the channels currently connected to MerchantOps through a hosted chat agent — today, that means channels connected via MerchantOps in Microsoft Teams (Hosted Agent).
Only Owners can see this page and disconnect a channel. See Team & roles.

​
The list

Each row is one connected channel, showing:
  • The platform (Microsoft Teams) and channel/team name.
  • Who confirmed the connection and when.
  • The underlying API key’s identity, for cross-referencing with Settings › API Keys.
  • An “Answers guests & external” badge if the Owner who connected the channel checked “Also answer guests and people from other organizations in this channel”. Otherwise the assistant only answers members of your own Microsoft organization. See Who gets answered.

​
Disconnect

Choose Disconnect on any row to remove that binding. This:
  1. Revokes the underlying API key immediately — not just disables it. There’s no grace period, unlike manually revoking a key from Settings › API Keys.
  2. Stops the bot from answering in that channel. The app and bot can stay installed in Teams; reconnecting later (@MerchantOps connect) mints a new key.

​
How this relates to API Keys

Keys created by a chat connect flow appear on Settings › API Keys too, labeled “Managed in Chat Integrations.” That label means:
  • The key cannot be rotated, re-roled, or manually revoked from the API Keys page — attempting any of those returns an error (HTTP 409).
  • It’s only managed here, from Chat Integrations, by disconnecting the channel.
This keeps a channel binding and its key from drifting out of sync — the key always exists exactly as long as the channel is connected.

MerchantOps in Microsoft Teams (Hosted Agent)

How a channel gets connected in the first place.

Server API keys

Keys you manage directly, and how “Managed in Chat Integrations” keys differ.