- Published on
GitLab Slack confidential issues: Stop unwanted alerts
- Authors

- Name
- Maruan
To stop confidential GitLab issues and notes posting to a broad Slack channel, open the GitLab for Slack app settings for the project, uncheck the Confidential issue and Confidential note triggers (or point them at a restricted channel), keep the merge request trigger on, and save. That is native GitLab configuration, not a MergeMe feature, and the steps below follow the official GitLab for Slack app documentation.
The catch: GitLab treats these as separate triggers from ordinary issue and note events. Turning off general issue alerts does not necessarily silence the confidential ones, and the reverse is also true. Don't guess. Find out who is actually sending, check whether settings are inherited, change the two triggers, then prove it with synthetic test content that contains nothing sensitive.
Short answer: turn off the two confidential triggers, keep the merge request one
In the GitLab for Slack app notification settings, each event has its own checkbox and its own destination channel name. Two of those events matter here: Confidential issue and Confidential note. Clear both checkboxes, or give each one the name of a restricted channel instead of your broad team channel. Leave the Merge request event checked and pointed at the channel you want. Use Test settings, then Save changes.
That is the whole fix for the app. The rest of this post covers how to confirm you are editing the right place, and that nothing else is posting to the same channel.
GitLab event
|
+-- Merge request ---------> broad channel (keep)
+-- Confidential issue ----> off, or restricted channel
+-- Confidential note -----> off, or restricted channelWhat the GitLab for Slack app treats as confidential events
The app lists two confidential triggers, and they behave differently from what many people assume. Confidential issue covers activity on confidential issues. Confidential note covers internal notes, or comments on confidential work items. So a comment on a confidential issue is governed by the note trigger, not the issue trigger.
That answers the common search about confidential comments posted to Slack. If comments from confidential work are showing up, the Confidential note checkbox is the first suspect, and an internal note on an otherwise ordinary issue can trip it as well.
Two things the documentation does not give you, so don't assume them. There is no separate Confidential merge request trigger in the list, and nothing syncs GitLab visibility to Slack channel membership. Slack channel access is whatever you set in Slack. Review both the event triggers and destination channel membership before sending confidential activity.
Step 1: inventory who is actually sending to the channel
Before changing a checkbox, find out which sender produced the message. Open the offending Slack message and note the app name or bot name that posted it. Then list every path that could write to that channel:
The GitLab for Slack app, configured per project or inherited from a group.
The older, deprecated Slack notifications integration. The docs say it is hidden from a project's integrations list under certain conditions once the app is installed, so it may exist without being obvious.
A custom webhook pointed at a Slack incoming webhook URL.
CI jobs that post to Slack from a script.
The app setting only controls the first. If the message came from one of the others, editing the app triggers changes nothing. That's why teams often disable a checkbox and still see the alert reappear. Write down the project, the sender and the destination channel before moving on.
Step 2: check whether the settings are inherited or custom
Open the integration in the project. Check whether it uses default settings or custom settings. This decides where you should make the change.
If the project inherits group or organization defaults, a project-level edit means switching that project to custom settings, which detaches it from future default changes. If many projects feed the same broad channel, fixing the group default is the cleaner move, and it needs someone with permission to manage group integrations. Don't override a group default from one project just because it's faster. The other projects will still leak.
For more on how defaults and overrides interact, see GitLab Slack integration group defaults. For the official rules, the integrations page above is the reference.
Step 3: disable or reroute the confidential triggers and save
Go to the project or group settings, open the GitLab for Slack app integration, and find the notification events list. The documentation says each event has its own checkbox and destination channel field.
Pick one of two paths per trigger:
Disable. Clear the Confidential issue and Confidential note checkboxes. Nobody gets these in Slack, and people rely on GitLab itself for confidential work.
Reroute. Keep the checkboxes on and type the name of a restricted channel in each destination field. If that channel is private, the GitLab for Slack app must be added to it first, or posts will not arrive.
Confirm the Merge request checkbox is still on and its channel is the broad one. Then use Test settings, then Save changes. Disabling is the safer default. Rerouting is only as private as the channel membership you maintain in Slack, and GitLab will not keep that in step with project access for you.
Step 4: test with synthetic issues and comments (a proposed matrix)
Prove the change with content that contains nothing real. Create throwaway items in a test project that has the same settings, or in the affected project if you must, with obviously fake titles. This matrix is a proposal for you to run, not results we have already observed.
Ordinary issue. Expected: follows your general issue trigger setting.
Confidential issue. Expected: nothing in the broad channel; arrives only in the restricted channel if you rerouted.
Public comment on an ordinary issue. Expected: follows the general note trigger.
Internal note. Expected: nothing in the broad channel; restricted channel only if rerouted.
Add a fifth check: open a test merge request and comment on it to confirm merge request alerts still flow. Wait for each event to settle before the next so you can tie every Slack message to its cause. If something appears where it shouldn't, go back to Step 1 and look for a second sender before touching the checkboxes again.
Other senders the app setting does not cover
Changing the app's triggers does not reach anything that doesn't use the app. Re-check the three independent paths from Step 1. A deprecated Slack notifications service can still hold its own trigger options. A custom webhook sends whatever event types it was subscribed to, and a leaked or old URL keeps working; for that case see GitLab Slack webhook security. CI jobs post whatever the script writes, regardless of any checkbox.
Also check who can see the destination. A restricted channel is only restricted if its member list is. The channel permissions audit guide covers that review. Treat each sender as its own configuration to inspect, because none of them inherits your fix.
If confidential content already reached the channel
Deal with exposure first, then cause. Restrict further access to the channel or stop the sender, tell whoever owns your incident process, and let that process decide on notification, scope and retention. This is operational guidance, not legal advice.
Deleting the Slack message is reasonable, but it doesn't settle things. Workspace exports, retention settings, search indexes and anyone who already read or copied the text are outside what a delete guarantees. Don't promise stakeholders that history has been purged. After containment, apply Steps 1 to 4 so the same content can't post again.
Optional: a quieter merge request view in Slack
Once confidential triggers are off, the broad channel is mostly merge request traffic, and that traffic is a separate noise problem. MergeMe is a Slack app that shows each GitHub pull request or GitLab merge request as one updating card instead of a stream of separate messages, and it works with GitHub.com, GitLab.com and self-hosted GitLab in one workspace.
Configure confidential issue and note triggers in the native GitLab app settings above. If your concern after this cleanup is merge request volume, see GitLab Slack duplicate notifications during migration for a related pattern.
Treat the trigger list as an access control, then test it
A checkbox is not a privacy model, so verify it. Clear Confidential issue and Confidential note at the right level of settings, keep Merge request on, and run the four-item synthetic matrix before trusting the channel. If merge request volume is what's left to tame, try the free Hobby plan at MergeMe, which posts one updating card per merge request on GitLab.com or self-hosted GitLab.
FAQs
How do I stop confidential GitLab issues and notes posting to Slack?
In the GitLab for Slack app notification settings, clear the Confidential issue and Confidential note checkboxes, or set each one's channel to a restricted channel. Keep the Merge request checkbox on, use Test settings, then Save changes. Also check for other senders, such as webhooks or CI jobs, which this setting does not control.
Does the Confidential note trigger cover comments on confidential issues?
Yes. According to the GitLab documentation, the Confidential note event covers internal notes and comments on confidential work items. That is why disabling only the Confidential issue trigger can still leave comments appearing in Slack. Turn off both, or route both to a restricted channel.
Is there a Confidential merge request trigger in the GitLab for Slack app?
No such trigger appears in the documented notification events list. The GitLab for Slack app provides options like Confidential issue, Confidential note, and Merge request events alongside standard Issue and Note triggers. To keep merge request alerts while silencing confidential activity, leave the Merge request checkbox on and change only the two confidential ones.
Why do confidential alerts still appear after I unchecked the triggers?
Another sender is probably posting. Other integrations or automated scripts posting to Slack may need to be adjusted separately. Identify the app or bot name on the Slack message, then inspect that sender's own configuration. Check whether the project still inherits group defaults or uses custom settings; group changes apply to projects using defaults, not custom overrides.
Can I route confidential issue alerts to a private Slack channel instead?
Yes. Enter the private channel's name in the destination field for each confidential trigger, and add the GitLab for Slack app to that channel first so it can post. The channel's Slack membership then becomes your access control, so audit it. MergeMe is not involved here; this is native GitLab configuration.