Slack workspace approval

Connecting a Slack workspace normally means you, personally, click through Slack's install screen. Sometimes that's not practical: the workspace belongs to a client, a different team, or someone who isn't otherwise going to use ThreadBridge. For that, ThreadBridge can hand the connection off to whoever is a member of that workspace, without asking them to create a ThreadBridge account.

If you're setting up the bridge

From the dashboard, next to Connect Slack, choose Send an approval link. That page gives you a link to send to a member of the workspace, along with a summary of what they'll be asked to approve.

The link is a signed, single-purpose token that identifies your account, not a session, so it works for someone who has never signed in here. It expires after seven days; generate a fresh one if it lapses.

If you're the one approving

Opening the link shows what's being requested and a button that hands you off to Slack's own install screen, signed in as yourself. Slack, not ThreadBridge, asks you to approve the permissions, which are the ones listed in Connect Slack: read channel names and messages, and post messages.

Approving returns you to a confirmation page. Nothing else is asked of you, and you don't need a ThreadBridge account. The person who sent you the link can then finish setting up their bridge.

How this differs from Microsoft's admin approval

Slack has no separate "approve for the whole workspace" step the way Microsoft does; whoever installs the app grants its permissions in the same screen, and that's the entire approval. There's no second, tenant-wide consent to chase down afterward, which is why this flow finishes in one hop where Microsoft admin approval takes two.

If the workspace is already connected

Same rule as connecting it yourself: a Slack workspace can only belong to one ThreadBridge account. If the person approving sees an error rather than a confirmation, the workspace is already claimed elsewhere; see Connect Slack for what to do next.