[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-slack-api-changelog-2026-06-17-system-notifications-now-sent-from-slack-user-uslack":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"slack-api-changelog","Slack API","slack","changelog-html","rest","https:\u002F\u002Fapi.slack.com\u002Fchangelog",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KVB8DSJ3BYSP6V4J0TG7P3S7","2026-06-17-system-notifications-now-sent-from-slack-user-uslack","Breaking","System notifications now sent from \"Slack\" user (USLACK) instead of Slackbot","Slack system notifications (channel membership changes, User Group updates, Slack Connect alerts, retention policy notices) are now delivered from the **\"Slack\" system user** (`USLACK`) instead of Slackbot, and historical Slackbot system notifications will be backfilled\u002Fmoved to the new DM. Apps that filter events by Slackbot's user ID, check the `username` field for `\"Slackbot\"`, or expect system notifications to route through Slackbot must be updated to handle `USLACK` instead. This is tagged as a **breaking change** by Slack.","2026-06-17T17:00:25.539Z"]