<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=560802) </details> <!--IssueSummary end--> ## Summary Add the ability to configure which GitLab users can trigger Slack notifications through inclusion/exclusion lists, providing granular control over notification sources. ## Problem Statement Organizations using GitLab's Slack integration receive notifications for all user activities that match configured event types. However, many teams have service accounts, automated tools, and CI/CD systems that generate high-volume, low-value notifications. Currently, there's no way to filter notifications based on the user who triggered the event, leading to notification fatigue and reduced effectiveness of the integration. ## Proposed Solution Implement user-based filtering controls for Slack integration notifications with the following capabilities: ### Core Functionality * **Inclusion List**: Define specific users whose actions will trigger Slack notifications * **Exclusion List**: Define specific users whose actions will NOT trigger Slack notifications * **Default Behavior**: When no filters are configured, all users trigger notifications (maintains current behavior) ### Configuration Options * **Per-Event Filtering**: Apply different user filters to different notification event types * **Global Filtering**: Apply the same user filter across all enabled notification events