Troubleshooting a connector
Start in Settings ▸ Connectors (click your name at the bottom of the sidebar). Each connector's row shows its state next
to its name.
"Authorization expired"
The service stopped accepting Chat with Work's access. Common reasons: you changed your password, an admin removed the
app, you revoked it in the service's own settings, or the grant simply ran out. When this happens, a Reconnect your
services window also pops up in the app.
Click Reconnect on the row and sign in again with the same account. If reconnecting fails straight away, check with your
IT admin that the service still allows Chat with Work.
Microsoft says it needs an admin's approval
Teams always needs a Microsoft 365 admin to approve Chat with Work, because reading channel messages requires it.
SharePoint and Outlook often do too, depending on your organization's Microsoft settings. Until then, Microsoft shows
"Need admin approval" and the connection is cancelled.
Ask your Microsoft 365 admin to do one of these:
1. Connect the service in Chat with Work themselves and, on Microsoft's consent screen, tick Consent on behalf of your
organization before accepting.
2. Or, in the Microsoft Entra admin center, go to Identity ▸ Applications ▸ Enterprise applications, open Chat with
Work, then Security ▸ Permissions, and choose Grant admin consent. The app appears there once someone in the
organization has tried to connect.
After that, everyone connects their own account, and each person still reads only what they can already see.
It won't make changes
- "Your organization lets connectors only read." An owner or admin has turned off Connectors can make changes in
Settings ▸ People. Ask them.
- "Reconnect to let it make changes." You switched to Read and change, but the service hasn't granted the extra
permission yet. Click Reconnect. For some services an admin may need to approve it.
- The connector is at Read. Switch it to Read and change under its row.
Settings, People: Connectors can make changes, the switch owners and admins turn off to keep every connector reading
only
"Paused"
The connector was paused, from Settings or from a new chat. The assistant leaves it alone until you click Resume.
A paused MCP server's row in Settings: Paused next to its name, and a Resume button
On a new chat, a paused service shows dimmed below the composer, with a pause badge. Click it and choose Resume.
A paused service on a new chat, dimmed with a pause badge, next to Connect
"Needs setup"
Some services need an owner or admin to set them up once for the whole organization, with an app they create in that
service. The row tells admins what to paste in. Members can connect once that's done.
The assistant didn't search it
Check the row says Connected, not Paused or expired. With several accounts of one service, ask for the one you mean by
name. The assistant can use a connector from the next question after it's connected or resumed.
Still stuck? Click the chat bubble in the corner of the app, or write to support@chatwithwork.com, naming the connector
and roughly when it failed.
