Unblock Slack and get into your workspace

Your browser never talks to Slack. It talks to TrickyBird, which fetches the page over its own connection and rewrites the HTML, CSS, and JavaScript on the way through, so every link and request inside the page points back at TrickyBird’s address instead of out at Slack. A small script stays behind in the tab to catch whatever the client asks for later, which on Slack is nearly everything. That is why a filter on the network has nothing of Slack’s to match on: what leaves your browser is addressed to TrickyBird.

Getting into a workspace is not one page but a walk across hosts. It starts at slack.com, hands you over to app.slack.com, and finishes on your workspace’s own host (the one with your team’s name in it). That handoff is where a proxy breaks quietly, because the host taking it is stricter about where the request appears to have come from than the host that sent you. Arriving through TrickyBird’s address, like everything else on the page, is what ends the walk at your workspace’s sign-in instead of an error page.

Yes, and it is Slack’s own way in rather than anything TrickyBird arranges: you give the address on the account, Slack sends a code to that mailbox, you type it back, and Slack decides whether to let you through. TrickyBird adds no sign-in of its own and does not get around Slack’s.

The same as always. Slack sees a connection arriving from TrickyBird rather than from your own address, so the route does change. Signing in is a separate matter. The moment you do, Slack knows which account is talking, and your workspace’s admin tools show your activity as they otherwise would. A proxy changes the route, not who you are once you have named yourself.

Cookies from the site you open stay in a server-side store keyed to your session, and everything in it is cleared about an hour after the last cookie written there. To run the service and curb abuse, the edge keeps a shortened form of your IP address, the hostname of the site you connected to, and basic response details, kept for at most 48 hours, with no TrickyBird account for any of it to attach to. Our security page sets that out in full.

One habit is worth forming before a work account goes through any of this: open one sensitive site per session. Everything you open in the same session arrives through the same TrickyBird address, so your browser treats it all as a single site underneath, and the separation between them is tidiness rather than a security wall. A fresh session, or a new private window, keeps a work Slack apart from the rest.

Whoever runs the network decides that, and it is a rules question rather than a legal one. If the network belongs to an employer or a campus, its acceptable-use policy is the document that applies, not the law. Read it before you decide: knowing what the rule says is not the same as being told to break it.

A second line is Slack’s own. Where Slack itself limits who it can serve, that is Slack’s restriction rather than a network block, and TrickyBird is not a way around it. Our Acceptable Use Policy says where we stand, and the guide on proxies and the law covers the rest.