Operational alerts
Open Settings → Admin → Workspace → Operational alerts. This page is about the things Twelfth relies on breaking — not about your business. When a chat surface refuses Twelfth’s credential, or an integration can no longer refresh the access you granted, Twelfth emails the people named here with what broke and what to do. Owners and admins can see and change it.
This is different from Briefings & alerts, which are the commercial alerts — decide-today, above-threshold escalations, the weekly digest — and from each person’s own Notifications.
Why this exists
A bot that has gone quiet looks exactly like a quiet week. A Google grant that stopped refreshing looks like a workspace that simply has nothing new. Nothing inside the product says otherwise, because from inside the product nothing is happening. So the moment a platform refuses Twelfth for your workspace — a Slack app revoked when an admin leaves, the Teams app removed from a team, Google returning invalid_grant on a token refresh, an Outlook grant expired — Twelfth records it and emails your ops contacts, before anyone notices a bot not answering or a number gone stale.
At most one email a day per problem. It stops on its own when the next answer, refresh or reconnect succeeds.
Who is told when something breaks
By default every owner and admin of the workspace with a verified email address. To send these to a specific inbox instead — IT, security, an on-call address — choose Change and enter the addresses, up to ten, comma-separated. Leave the list empty to go back to every owner and admin. The page always shows the list an email would actually go to, not the rule.
One list covers everything: Slack, Google Chat and Microsoft Teams, and every integration Twelfth holds a credential for.
What is watched
Every chat surface the workspace has turned on and every integration it has connected, each with its standing right now: working, or the problem Twelfth has found against it and since when. A Google grant that also carries the Chat permission appears twice — once as the data grant, once as the chat surface — because each can break on its own. Each row links to where it is reconnected.
Recent alerts
What has broken for this workspace in the last thirty days, open problems first, with when each was first seen, when the contacts were last emailed, and when it recovered. A repeat after a recovery is a new alert and emails again.
What the email says
The subject names the subject and the problem — Slack is refusing twelfth’s credential, twelfth’s access to Google has lapsed. The body says what it means for the workspace (people asking there get nothing back; anything that reads from the integration goes stale), the one thing to do, what the platform said if it said anything, and a button to the page where it is fixed. The footer links back here to change who receives them.
Related
- Comms & chat — the chat surfaces themselves, each with its own Health panel
- Integrations — the systems Twelfth reads from
- Briefings & alerts — the commercial alerts, which are a different thing