Slack

One Slack connection, two uses: offline alerts posted to a channel, and apps that read from Slack.

Slack is the one integration that spans two purposes. Connect it once and both work.

Alerts into a channel

Connect Slack under Settings > Integrations > Slack and authorize. Then go to Settings > Notifications, open Slack under Screen status alerts, pick the channel, and choose which events to alert on. If Slack isn't connected yet, the page says so, with a Connect Slack link to the integration.

Until you pick a channel, it shows No channel selected and nothing is posted. That is the most common reason for a Slack connection that appears set up and never says anything.

To move alerts to a different channel, turn off Slack alerts and set them up again. Turning them off asks you to confirm.

Pick a channel of its own rather than a busy one. Screen alerts among deploy notifications and standup reminders get muted along with everything else.

Apps that read from Slack

The same connection lets an app pull from a Slack channel, so what a team is posting can appear on a screen. An app that needs a channel offers a picker of the channels available to the connection, so there is no channel ID to look up. If Slack isn't connected, the setting shows Connect to Slack, which takes you to Settings > Integrations.

That is a different job from alerting, and it is worth being deliberate about the channel: anything posted there is on a wall.

Workspace-level, not personal

The connection belongs to the Screenly workspace, not to whoever authorized it.

Before July 2026 it was per person. Workspaces where several people had each connected their own kept exactly one after the change, so if your Slack alerts stopped around then, this is why. Reconnect once for the workspace.

Disconnecting

From Settings > Integrations > Slack, after a confirmation. Alerts stop and any app reading from Slack stops showing data. You can also revoke Screenly from the Slack side, which has the same effect.