What is Slack Active Status?

Understanding Slack Active Status

The green dot in Slack indicates you've recently interacted with the application through typing, clicking, scrolling, or other input. Slack continuously monitors these activity signals and displays active status when it detects engagement. Understanding exactly what counts as 'activity' is essential. Slack registers the following as valid activity signals: typing in any message input field (channels, DMs, threads), clicking on channels, messages, or UI elements within Slack, scrolling through message history or channel lists, and using keyboard shortcuts within the Slack window. Critically, these actions must occur within the Slack application itself. Typing in Google Docs, clicking through a Jira board, scrolling a web page, or even moving your mouse across a visible-but-unfocused Slack window does not count. Slack only detects input that the Slack client process directly receives. After your last qualifying interaction, active status persists for roughly 10 minutes before transitioning to away. This persistence window is not configurable and has never been officially documented by Slack, though the behavior has remained consistent for years. The 10-minute window is a countdown that resets with each new interaction. If you click a channel at minute 8, the timer starts over from zero. But if you switch to another app at minute 0 and do not return, the green dot will disappear at approximately minute 10. Several conditions kill active status instantly, without waiting for the 10-minute timer. Locking your screen (manually or via a corporate idle policy) causes the Slack desktop client to detect the lock event and immediately signal the server. Closing your laptop lid disconnects the WebSocket, and the server marks you away within seconds. Force-quitting or closing the Slack app terminates the connection entirely. Network disconnection — whether from a WiFi drop, VPN timeout, or ISP outage — severs the WebSocket and triggers immediate away. On mobile, switching away from Slack causes iOS or Android to suspend the app within a few minutes, which drops the connection. Under the hood, Slack's activity detection relies on WebSocket heartbeats combined with interaction events. The desktop app monitors window focus and direct input like keystrokes, mouse clicks, and scrolling within Slack. The browser client uses the Page Visibility API, which means background tabs may stop registering as active even if Slack is technically open. On mobile, presence depends on whether the app is in the foreground. These per-device signals are evaluated independently, and Slack shows you as active if any connected client reports recent interaction. For knowledge workers, this creates a structural mismatch. Most productive time is spent outside Slack in IDEs, document editors, spreadsheets, and video calls. None of that activity registers. The green dot disappears during exactly the kind of deep, focused work that organizations value most. Manually setting yourself to active through Slack's menu offers only temporary relief. The underlying API call (users.setPresence) accepts 'auto' or 'away' but has no permanent force-active option. The server re-evaluates presence on the next heartbeat cycle and reverts to its own assessment within minutes.