Skip to content
ABRAM

Last updated October 29, 2026

Section 6.1: Slack Notifications

Connect your Slack workspace once and ABRAM posts project updates to the channels you choose. Your organization has one Slack connection, managed from Settings > Integrations > Connectors. Nobody has to connect Slack for themselves. ABRAM matches each person to their Slack account by email.

Slack is available on Pro and above. Owners and admins connect and manage it.


1. Connecting Slack

  1. Open Settings and go to Integrations > Connectors.
  2. Find the Slack row and click Connect Slack.
  3. Slack opens. Choose the workspace and click Allow.
  4. You return to ABRAM and the row shows Connected.

If you are a member without admin rights, the row reads "Ask an admin to connect Slack."

How People Are Linked

Once Slack is installed, ABRAM looks each person up in the Slack workspace by email the first time they open Connectors, and when they click a button in a Slack message. Direct messages reach a person once that match is made. If nobody in the Slack workspace uses your email, the row tells you so and Slack cannot message you. Ask an admin to invite that email address to the Slack workspace.


2. Choosing Where Updates Go

Click Manage on the Slack row to open the Slack sheet. Every change saves as you make it. There is no save button.

Notifications

  • Post to Slack: the master switch. Turn it off to stop all posts without losing your routing.
  • Default channel: choosing a channel here sends every category to it. Start here, then change individual categories below.

Routing

Each category of update has its own channel:

CategoryWhat it covers
General updatesEverything that does not fall in another category
MilestonesMilestones, completed work packages and completed projects
Deliverables and reviewsDeliverable updates, approvals and revision requests
Financials and invoicingInvoices, payments and billing
Logistics and bookingsWork orders, booking conflicts and published call sheets

Pick Do not post for any category you want kept out of Slack. Private channels appear in the list with (private) after the name.

Creating a Channel Without Leaving ABRAM

  1. Click the + next to a channel list (Create a Slack channel).
  2. Type the new channel name.
  3. Click Create channel.

The new channel is selected for that category straight away. If a channel with that name already exists, ABRAM uses it.


3. Routing One Project Somewhere Else

A project owner, or an organization owner or admin, can send a project's updates to its own channels.

  1. Open the project and click Project settings (the gear in the project toolbar).
  2. Go to the Slack section.
  3. Turn on Slack notifications.
  4. For each category, choose a channel, or leave it on Inherit to use the organization's routing.
  5. Click Save changes.

A category set on the project wins over the organization's setting for that project. A category left on Inherit goes to the project's General updates channel when one is set, and follows the organization's routing otherwise.


4. Acting From Slack

Some messages carry buttons, so you can act without opening ABRAM:

  • Deliverable messages: View Deliverable, Approve and Request Revision. Approving or requesting a revision needs an organization owner or admin.
  • Work order, call sheet and booking conflict messages: View Details and Mark On-Site (Check-In), so crew can check in from Slack. Only the crew booked on the shift, or whoever runs the project, can check in.

When you click a button, the message updates in place to show what happened and who did it. If your Slack account is not linked to ABRAM yet, Slack replies with a link to connect it first.


5. Your Own Slack Messages

Direct messages to you are set per person under Settings > Notifications, in the Slack DM column. When an admin turns Post to Slack off, those switches lock and show that an admin turned Slack off for the organization.


6. Reinstalling or Disconnecting

At the bottom of the Slack sheet:

  • Reinstall runs the Slack install again. Use it if Slack permissions changed or posts stopped arriving.
  • Disconnect removes ABRAM from your Slack workspace and stops all posts. Your channel routing is kept, so reinstalling later picks up where you left off.

Troubleshooting

The Slack row is missing from Connectors. Slack is on Pro and above. On Free the row does not appear.

ABRAM says it could not connect Slack. The email address on your ABRAM account has to belong to a member of the Slack workspace you chose. Ask a Slack admin to invite that address, or choose the workspace your email already belongs to, then click Connect Slack again.

The channel list will not load. The sheet shows the error with a Retry button. If it keeps failing, click Reinstall.

Posts are not arriving in a channel. Check that Post to Slack is on, that the category is not set to Do not post, and that the project has not overridden the channel in Project settings.