Connect Slack in Integrations
Open Settings → Integrations (Integrations) and find the Slack notifications section to connect a workspace and link your account. Choose notification channels for a site in Edit site, after the site exists. Slack is available on all plans, including Free and accounts with one organisation. For multiple organisations, select the correct organisation and check its name before setup.
An organisation administrator with current membership can connect a workspace and manage site channels. Other organisation members can link their own Slack account. Sentinel provides the Slack app: customers authorise it in Slack and do not enter app secrets or bot tokens in Integrations. Your Slack workspace may require an administrator to approve installation.
- Select Connect Slack workspace. If prompted, enter a fresh multi-factor authentication (MFA) code, then choose the intended workspace in Slack and authorise Sentinel. Complete the connection within five minutes. If you cancel authentication, select Connect Slack workspace again when ready. If you cancel in Slack or the connection expires, start a new connection from Integrations.
- Return to Integrations. Select Link my Slack account and run the exact displayed command in the connected Slack workspace from your own account within five minutes. Keep the code private. If it expires, select Link my Slack account again to get a new command. Select Refresh Slack status to check the link. Connecting a workspace does not link your account automatically.
Choose channels for a site
- Open Sites, open the site, select the Setup tab and select Edit site. Find Slack notifications for this site. The Integrations link in this section opens a new tab so you can complete workspace setup. Return and select Refresh Slack availability afterwards.
- Set Site Slack notifications to Choose channels for this site. Select a connected Slack workspace where your account is linked. In Slack, open the channel details → Agents & apps → Add agents and apps, and add the Sentinel app connected to this workspace. Slack menu names may differ. Return to the site form, select Refresh channels, then choose the Slack channel. Use More channels and First channels to find the intended channel.
- For a public channel, select the public-sharing consent checkbox. Choosing another workspace or channel clears this consent. Check the audience rules below.
- Enable Include administrator-only notifications if the channel must also receive certificate alerts. Connection and security-update alerts do not need this option. Use Add another Slack channel for additional destinations, up to ten. Select each workspace/channel pair only once.
- Save the site. If prompted, enter a fresh MFA code. Cancelling authentication does not save your changes; save again when ready. The site and its channel choices save together. If Slack validation fails, the form keeps your choices so you can correct them and retry. No test is sent by saving. If the site or its Slack settings changed while you were saving, reload the site and review the current choices before trying again.
- Reopen Edit site to see Saved channel delivery status. Use Send test to… for a saved active channel, then Refresh delivery status and check Slack. Tests and status apply to saved site channels and are hidden while Slack changes are unsaved. Sending a test does not require a fresh MFA code. A queued test is not delivery confirmation.
Supported automatic Slack notices are:
| Notice | Include administrator-only notifications required? |
|---|---|
| A site has never sent data, has stopped sending data, or is reporting again | No |
| A security update is needed | No |
| A certificate is expiring, expired, invalid, or valid again | Yes |
Observed releases and confirmed security fixes are not sent to Slack. Review these in the site's History and Updates tabs.
Each site has independent channel settings. These destinations receive notifications for that site, not notices without a site or whole-organisation digests. Choosing a channel for one site does not change another site's choices.
Keep existing settings or turn Slack off
Keep existing settings leaves Slack unchanged when you save other site details. If the site inherits older organisation channel rules, Edit site lists the applicable channels. New sites can also inherit those rules when Slack is left unchanged.
Saving Choose channels for this site replaces inherited Slack routing for that site. Saving Off for this site stops its Slack notifications, including inherited rules, without changing other sites or webhooks. Removing all channel rows also turns Slack off when saved. Previously queued alerts are checked against the current site settings before sending; historical alerts are not backfilled. Keep existing settings preserves an already saved Off choice; it does not restore inheritance.
Use Discard Slack changes to return to the saved configuration and save other site details without changing notifications. If availability or saved settings cannot be loaded, leave Slack unchanged, or discard your Slack changes. Use Retry site notifications when offered. An empty list, loading state or failed request does not mean notifications are off.
If a site is moved to another organisation, its site channels are turned off. An administrator in the new organisation must configure them after the move.
Private and public channels
For a private channel, every member other than the Sentinel bot must link their own Sentinel account and remain a member of this organisation. A channel receiving administrator-only notifications must contain only linked organisation administrators and the Sentinel bot. Unlinked people or other bots prevent delivery.
Public channels require the Allow notifications in this public channel consent checkbox. People outside this Sentinel organisation may be able to read the messages. This consent also permits a wider audience for administrator-only notifications if that separate option is enabled. Site selection limits which sites send notifications; it does not limit who can read the channel. The administrator responsible for the destination must keep their Slack account linked and retain organisation administrator access.
Shared channels, Slack Connect channels, pending shared channels, archived channels and direct messages are not supported. The bot must remain in the channel. Sentinel checks channel access and current authority again before delivery; membership changes can stop messages.
Recover a connection
An organisation administrator can keep or reduce the notifications on an already active channel saved for this site, even if the workspace is disconnected or their own Slack account is not linked. This keeps the previous administrator responsible for the route and does not restore delivery. New channels, reactivating a channel, or enabling more notification or sharing options require a connected workspace, your linked account and fresh channel checks. Inherited organisation rules do not qualify as saved site channels.
If workspace access was revoked, connect the workspace again in Settings → Integrations, link your account if needed, then review and save the site's channel choices. Check current organisation roles, account links and the bot's channel membership when delivery is refused. Each private-channel member must keep the required access.
If Slack is disabled or setup is unavailable, the form explains the condition. Contact support for environment setup. If no connected workspace is available to choose, complete workspace connection and account linking in Settings → Integrations, then refresh Slack availability. An organisation administrator must manage channel choices; other members keep existing settings.
Commands and other integrations
Linked members can use /sentinel status ORGANISATION_ID and /sentinel messages ORGANISATION_ID in a connected channel. Use the command name shown by your environment: production uses /sentinel; UAT uses /sentinel-uat after its command setup is complete. Keep the rest of the command unchanged. If Slack opens the wrong app or rejects a newly generated link command, check the workspace and ask Sentinel support to check the app command configuration. Do not share the link code. Replies are visible only to the person who ran the command and respect their current access. Commands do not start scans, apply patches or deploy changes.
Signed webhooks, read-only integration credentials and manual status digests remain API features. Integration credentials are separate from site keys on Connector keys. Ask your organisation administrator to arrange these. Site channels do not receive whole-organisation digests. Older organisation destinations remain API-managed; editing a site does not change their settings for other sites.
Authorised Slack commands and successful account linking create audit records for the organisation. Its administrators can review these in Audit log with that organisation selected. They do not appear in My account, including for the member who ran the command. The records identify the linked Sentinel account and request result; they do not contain the command text, link code or reply contents. An audit result does not prove that a site is healthy or that someone read a reply.
A status digest reports current assessment states and recent open notices. Unknown, pending, partial, failed or stale evidence is not an all-clear result. An empty message list or a successful connection test does not prove a site is healthy. A weekly digest schedule is not available through this integration setup yet.
If messages stop, ask your administrator to check the destination, account links and current membership. A delivery marked accepted means the provider accepted it; it does not prove someone read it. A delivery marked uncertain may already be in Slack, so check the channel before requesting another.