Slack Active on Multiple Devices: Which One Sets Your Status?
When you use Slack on a phone and a computer at once, one active device keeps you green, and a manual away set on any device makes you away on all of them. We measured connection_count per browser tab and a manual away across four connections.
On this page
When you are signed in to Slack on several devices, Slack shows one dot for all of them. If any one device is active, you show as active. A computer counts as active for 10 minutes after your last keyboard or mouse input in any app, and a phone counts only while the Slack app is open on screen. You show away only when every device is idle, asleep or closed. One setting overrides all of that: Set yourself as away on any device makes you away everywhere until you undo it.
We tested the two parts we could measure on 3 October 2026, in our own workspace through Slack's presence API: how Slack counts devices, and what a manual away does to the other ones.
What Slack counts as a device
Every open Slack client is its own connection: each desktop app, each browser tab and each phone with Slack running. Slack reports the number for your own account as connection_count. We opened Slack in more browser tabs and read it after each one:
07:39:38Z baseline (2 Slack tabs already open) connection_count: 2
07:40:04Z opened a third tab connection_count: 3
07:40:23Z opened a fourth tab connection_count: 4
07:41:37Z closed our two tabs connection_count: 1
(Another tab closed during the last minute, so the count fell to 1, not 2.) Each new tab also moved last_activity to the moment it connected. So any forgotten tab or second computer is one more connection that can count as active.
A manual away covers every device
With four connections open, we set the account to away through one client, the way Set yourself as away does. Slack's presence API answered at once:
07:40:34Z presence: away manual_away: true connection_count: 4
07:40:37Z presence: active manual_away: false connection_count: 4 (after "auto")
A second tab, which had not done anything, switched to away as well. Its profile menu showed Away and offered Set yourself as active:
Clicking around in that tab moved last_activity forward, yet manual_away stayed true. Activity does not end a manual away; only Set yourself as active, on any device, does.
The rule, step by step
- Manual away first. It is a setting on your account, not on one device, as the test above shows.
- Then any active device. Desktop app, browser tab and phone all count. One active connection makes you green.
- Otherwise away. When the last active device goes idle, sleeps or locks, you turn into an empty circle.
Do Not Disturb works the same on all devices. It adds a small z to your dot and pauses notifications, but it never makes you green or away; see the green dot with a z. The per-device timers are in how long does Slack stay active.
Common two-device situations
| Situation | Your dot | Why |
|---|---|---|
| Laptop idle for 15 minutes, Slack open on the phone screen | Green | The phone is an active device |
| Typing on the laptop, phone locked in your pocket | Green | The laptop is active |
| Laptop asleep, phone locked | Away | No device is active |
| Set yourself away on the phone, typing on the laptop | Away | Manual away covers every device |
| Two computers, one idle and one in use | Green | One active connection is enough |
| An old browser tab on a second computer | Green for 10 minutes after any input there | It is a connection too |
Never appear "away" on Slack again
Cloud-based. No downloads. Works 24/7 even when your laptop is off.
Can coworkers see which device you are on?
No. Being active on two devices looks the same as being active on one, and coworkers see no phone badge or device label; does Slack show when you are on mobile covers what they can still guess. Your own access log lists every sign-in with its client and IP, and Owners and Admins can see everyone's on paid plans; see does Slack track your location.
Where notifications go when you use several devices
By default Slack sends notifications to the desktop while you are active there, and to your phone once you are inactive on desktop. The delay is under Preferences, Notifications, "Send notifications to my mobile devices". If phone notifications never arrive, a desktop connection that still counts as active is a common cause; see Slack notifications not working.
Check your own connections
Call users.getPresence with your own user token. For your own account it returns connection_count and manual_away; for anyone else it returns only presence:
curl -s https://slack.com/api/users.getPresence \
-H "Authorization: Bearer $SLACK_USER_TOKEN"
If the count is higher than the devices you think you use, open my.slack.com/account/logs and use sign out of all sessions. It signs out every other session, your phone included, so keep the device you are using at hand. More on the API in the Slack presence API.
Using a second device to stay green
Because one active device is enough, a second one can keep you green while the main one is closed. A phone with Slack open on screen and auto-lock off does this until the battery or the OS stops it; the setup is in keep Slack active on mobile. Slack Green does the same with a session it runs for you, so the dot stays green with your laptop and phone off. Every option is compared in how to keep Slack active.
FAQ
Why does Slack show me away on my phone when I am active on my laptop?
It should not. Check whether a manual away is on, and whether the laptop is signed in to a different workspace. Presence is per workspace; see using several Slack workspaces.
Stop Jiggling Your Mouse.
Join hundreds of remote workers who never worry about their Slack status. Set it up once, stay green forever.
Related Articles
Slack Drafts: Where to Find Them, and What Happens When You Schedule, Archive or Leave
We wrote drafts in a channel, a thread and a DM in Slack web, then scheduled, sent, archived and left, and checked Drafts & sent and Slack's API after each step.
Slack Mark as Unread: Option-Click, the Menu, and What Clears It
We marked messages unread in a channel, a DM and a thread in Slack web, read the read state back from the API, and timed what clears it.
Slack Bot Scopes: The Scope Each API Method Needs, Measured on 44 Methods
We gave a Slack bot one scope, called 44 common Web API methods, and read the needed field of every missing_scope error. Then we added the scopes and called them again. The table shows which scope clears each method.