Send workspace notifications to a Slack channel
Last updated: October 13, 2026
Post your workspace's activity (new projects, finished trainings, team changes, usage alerts) to one shared Slack channel your whole team follows.
Before you start
- You need to be a workspace admin in Layer. Slack appears under Integrations in settings only for admins.
- Slack must be connected to the workspace, which needs permission to install apps in your Slack workspace. One connection does two jobs: the Layer agent answers in Slack threads, and notifications post to Slack. If it isn't connected yet, the steps below include it.
- Decide on the channel first. A dedicated channel, such as
#layer-activity, keeps notifications out of the team's discussion.
In Layer
-
Open the workspace menu, choose Settings, then select Slack under Integrations. The Slack Connection card shows Connected to and your Slack workspace's name.
If it isn't connected, select Connect Slack, then Continue with Slack, and approve the Layer app for your Slack workspace in the window that opens.
-
Select Select channel, type part of the channel's name and choose it.
-
On the channel's card, clear anything the team doesn't need to see. Here Billing is cleared so usage alerts stay out of the art channel, while Training stays on.
In Slack
Public channels need nothing more: Layer can post to them without being a member. For a private channel, add Layer to it first (type /invite @Layer in the channel), then open Select channel again. A newly added channel can take a few minutes to appear in the list.
What the team channel can receive
Changes save as you make them. Each category's box turns everything under it on or off, and the switch at the top right of the card pauses the channel without losing your choices.
Workspace
Project Created and Reference Set Created: someone in the workspace made a project or a reference set.
Training
Training Started, Training Complete and Training Failed: a reference set's training run began, finished and is ready to use, or failed.
Membership
Member Invited, Member Removed and Member Role Changed: changes to who is in the workspace and what they can do.
Billing
Usage Threshold, Auto-reload Succeeded and Auto-reload Problem: the workspace's Creative Unit usage reached a threshold, or an automatic top-up went through or needs attention.
Check that it works
Make a change that sends a notification you left on, such as creating a test project in Layer.
Look for Layer's post in the channel, with a button that opens the project in Layer. Delete the test project afterwards.
One channel per workspace
A workspace sends its notifications to one channel. To move them, select Disconnect on the channel's card, which stops posts to that channel and leaves Slack connected, then choose another channel.
A project doesn't have a channel of its own. When a team needs its own feed, two setups work:
- A workspace per team. A team that works in its own Layer workspace connects Slack there and picks its own channel.
- A person's channel. Anyone can send their own notifications, such as comments that mention them, to a channel instead of a direct message. See Choose how notifications reach you.
If something goes wrong
- There is no Slack in settings. Only workspace admins see it. Ask an admin, or for a role with admin settings.
- The channel isn't in the list. It is private and Layer hasn't been added to it, or it is archived. Invite Layer to the channel in Slack and try again in a few minutes.
- Failed to load Slack channels. Slack access may have lapsed. Reauthorize Slack in Connectors, then open the list again.
- Posts stopped arriving. Someone may have selected Disconnect on the Slack Connection card, which disconnects Slack from the whole workspace: the agent stops answering and nothing posts to Slack. Connect it again and pick the channel again.