Slack Notifications

Availability: Available to all Hiring Company accounts. Connecting your Slack workspace to BCS usually requires a BCS admin and a Slack workspace admin.

Overview 💬

BCS can now post compliance activity straight into a Slack channel your whole team can see. Instead of relying on one person to spot that a vendor's COI expired, the alert lands in #compliance (or whichever channel you choose) the moment it happens.

You control which events post, and how narrow the scope is for each one — all records, specific locations, or specific segments.

Watch the walkthrough 🎥

Team notifications vs. your personal notifications 🔔

BCS has two separate notification systems, and it's worth keeping them straight:

• Personal user notifications — the bell icon in the top-right corner of BCS. These are yours alone and only you see them. See User Notifications for how those work.
• General (team) notifications — configured in Client Settings and delivered to your whole team. As of this release, these are delivered to Slack.

This article covers general team notifications going to Slack.

Where to find the settings 📍

1. Click the gear icon in the top-right corner of BCS to open Client Settings.
2. Under GLOBAL in the left menu, select Notifications.

You'll land on the Notifications page: "Choose which events post to your Slack channel — and how narrow the scope is for each."

Step 1: Connect Slack 🔗

At the top of the page you'll see the Delivery channels section with a Slack card reading "Get notifications in Slack" and a status of Not connected.

1. Click Connect on the Slack card.
2. Authorize BCS in Slack and choose the channel that should receive notifications.

💡 Until Slack is connected, you can still flip toggles and set scopes, but BCS will show a reminder: "Connect Slack to route events to a channel." Nothing will actually be delivered until the connection is in place.

⚠️ Heads up: connecting Slack to BCS typically requires an admin on both sides. If the Connect step stalls, that's usually why — loop in your BCS admin.

Step 2: Turn on the events you care about ✅

Below Delivery channels, events are grouped into categories. Each event row has a Slack toggle and a scope dropdown.

1. Toggle Slack on for each event you want posted.
2. Set the scope for that event (see the next section).
3. Click Save changes.

A footer bar keeps a running count of unsaved changes — for example "4 unsaved changes across your notification preferences" — with Discard and Save changes buttons. Nothing takes effect until you save.

💡 To switch on an entire category at once, use Enable Slack for all at the top-right of that group.

Step 3: Set the scope for each event 🎯

The scope dropdown on each row controls which records can trigger that notification. You have three options:

• All records — every record in your portfolio.
• Specific locations — pick one or more sites or regions.
• Specific segments — filter by segment or category, then choose the segments you want in the Select segments picker.

Click Done to close the dropdown. The default scope for every event is All records.

💡 Scope is set per event, so you can post every COI expiration company-wide while keeping exception approvals limited to a single region.

📌 Note: Specific segments only works if you've already set up segments in BCS. If you haven't, set those up first and then come back to this page.

What you can be notified about 📋

This release ships with 7 event types across 2 categories.

Compliance

Record compliance status changes.

• Record became compliant — all Insurance Assignments for a record are now Compliant.
• Record became Non-Compliant — one or more Assignments have moved to Non-Compliant.
• COI soon to expire — a Certificate of Insurance is approaching its expiration date.
• COI expired — a tracked Certificate of Insurance has passed its expiration date.

Exceptions & Waivers

Approval workflow for requirement exceptions.

• Exception requested — a user has submitted a Request Exception that needs review.
• Exception approved — an approver has accepted the exception, and a Waiver pill is applied.
• Exception rejected — an approver has declined the exception, and the Assignment remains as-is.

Choosing your expiration warning windows ⏰

The COI soon to expire event has an extra control: a Notify at … before expiration row with options for 90d, 60d, 30d, 14d and 7d.

Click any of these to select or deselect it — selected windows are highlighted. You can pick more than one, so a single COI can generate a heads-up at 60 days, another at 30 days, and a final nudge at 7 days.

💡 Pick the windows that match how long your renewal chase actually takes. Selecting all five is a fast way to make the channel noisy.

Muting notifications 🔇

You don't have to switch everything off one row at a time:

• Mute group — at the top-right of any category, silences every event in that category.
• Mute all notifications — the master toggle near the top of the page. It pauses every channel until you turn it back off. Handy while your team is out, or during a bulk import that would otherwise flood the channel.

Starting over ♻️

Click Reset to defaults at the top-right of the Notifications page to return every event and scope to its original setting. If you've made changes you haven't saved yet, Discard in the footer bar reverts just those.

What's coming next 🚀

• More triggers. The 7 events above are the starting set. We're expanding the list, including more custom triggers.
• Microsoft Teams. Teams is on the roadmap as a delivery channel. It is not enabled as of this release, but it's coming.

Tips 💡

• Start narrow. Turn on two or three events for one location, see how the volume feels in Slack, then widen.
• Use a dedicated channel. A purpose-built channel like #coi-alerts keeps compliance traffic out of busier channels.
• Team notifications complement personal ones — they don't replace them. Your bell-icon notifications keep working exactly as before.
• Remember to hit Save changes. Toggles and scopes are staged until you do.

Questions? 🙋

Reach out to your BCS representative or contact support if you'd like help getting Slack notifications set up for your team.