Slack apologizes, says it has restored access to most of the accounts it has mistakenly blocked while trying to comply with US trade sanctions
Two days ago, we updated our system for applying location information to comply with U.S. trade embargoes and economic sanctions regulations.
Context & Ripple Effects
The apology closes a loop opened the day before, when Slack began deactivating accounts linked to Iran without warning users after updating its system for applying location information under US trade embargoes. The over-blocking was a direct product of that compliance change — location-based enforcement caught legitimate customers alongside sanctioned ones.
Sanctions enforcement is becoming a recurring operational event for Slack rather than a one-off: the same no-notice pattern reappeared years later when Slack cut off some Russian customers to satisfy US sanctions and parent company Salesforce's policies (Russia cutoff).
First-order effects
- Most of the mistakenly blocked users regain access to their workspaces, but the episode leaves Slack publicly accountable for a compliance tool that failed silently against its own customers.
Second-order effects
- Other collaboration platforms face pressure to add notice-and-appeal steps before sanctions-driven deactivations, since Slack's silent enforcement became the story instead of the sanctions themselves.
Third-order effects
- If location-data screening keeps producing false positives at scale, SaaS providers will need standardized appeal processes for sanctions blocks — turning export-control compliance from a back-office filter into a customer-facing workflow.
The trend: SaaS platforms are absorbing US trade sanctions into automated account-level enforcement, and each false-positive wave pushes them toward notice-and-restoration processes as standard practice.