Notifications and reports
Gatlas can tell a Slack channel when a sync fails, post a weekly digest or a board pack on a schedule, and answer a reporting question for a company. Nobody has to remember to check.
Connect a Slack channel for each company
Notifications are set up per company, or once for the whole organization. The owner connects Slack for the organization and for each top-level company. Admins and principals can also do it for companies nested under another company. Other roles do not see these settings.
Choose where alerts should go
Open Notifications in the sidebar. The list shows your organization and each company, with its Slack channel and a status of Not connected, Connected or Paused. Choose one.
Connect Slack yourself, or send an install link
Connect Slack takes you to Slack to approve Gatlas and pick a channel. If someone else administers your Slack, choose how long the link should last under Install link expires in (1, 3 or 7 days), then Create install link. The link is copied for you to send; they need no Gatlas account.
Send a test
Once connected, Send test posts a message to the channel. If Gatlas cannot post there, invite @Gatlas to the channel. Change channel, Pause and Disconnect sit beside it.
Alerts tell you the moment something needs a person
Open Alerts under the company and tick the events Gatlas should post about. When you connect a channel, every event except Anomaly detection starts ticked. The events:
- Sync failures
- Stale connections
- Token expiry
- Anomaly detection
- New connections
- New members
- New MCP keys
- Sync recovered
- Transform prompt failed
- MCP key first used
- MCP key revoked or changed
- Agent feedback
- Connection removed
- Member removed
Keep Sync failures, Stale connections and Token expiry on at least. A broken connection is fixed in minutes when someone hears about it, and found weeks later when nobody does.
Scheduled messages arrive on a rhythm you set
Open Scheduled messages under the company and choose Add scheduled message. Pick the Message:
- Weekly digest: connection health, sync activity and published views for the last seven days.
- MCP briefing: what AI assistants did with your data in the last 24 hours. It is skipped on days with no activity.
- Source health: which connections are failing or stale right now.
- Artifact: one of your artifacts, posted with a short intro and an Open artifact button.
Then set the Cadence (daily, twice daily, weekly or monthly), the Send time, the Timezone, and the Channel if it should go somewhere other than the connected one. Preview shows the message before you save. A channel connection holds up to 20 scheduled messages.
Every new channel comes with two: an MCP briefing every day at 09:00 UTC, switched on, and a weekly digest on Mondays at 09:00 UTC, switched off. Edit or switch off either one.
Tip
{artifact_name}, {artifact_description}, {scope_name} and {date}. Monthly board packs work well this way: build the artifact once, then schedule it for the first of the month.Agent reports answer a reporting question for a company
An agent report puts one question to an AI agent that reads a company and everything below it: its published views, documents and AI context. It cannot reach outside sources or change anything, and every answer cites the data it used.
Open Agent reports under the company
It appears once the company has a Slack channel connected. It is not available for the organization as a whole.
Ask the question
Fill in Reporting question, for example "How did gross margin develop this quarter, and what drove it?", and check Entity reporting timezone. Additional context is a note for the people reading the report later; the agent never sees it. Choose Run report.
Read the result
The run is queued and appears under Recent runs. Open it to read the report and the evidence behind it, choose Run again for a fresh answer, or Revoke approval to stop it.
Note