Slack

Bordio for Slack puts your work where the conversation already happens: personal notifications in your DMs, rich previews of Bordio links, and tasks you can create and update from a message.

What you get

Notifications — a direct message when a task is assigned to you, a meeting moves, someone comments, and so on. You choose which ones.
Link previews — paste a Bordio link and it expands into a card with status, assignees and dates.
Task actions — complete a task, change its status or assignee straight from the card.
Task creation — /bordio add, or turn any Slack message into a task.
Thread sync — replies in the thread under a preview become comments on the task, and vice versa.

Setup in three steps

Setup happens at three levels, and each one unlocks a different part of the integration.

1. Install the app (once, by an admin)

Someone with rights to manage the organization installs Bordio into your Slack workspace.

In Bordio, open Organization settings → Integrations.
On the Slack card, click Add to Slack.
Slack asks which workspace to install into and shows the permissions Bordio requests. Confirm — you’ll be returned to Bordio, and the card will show the connected Slack workspace.

One Slack workspace belongs to exactly one Bordio organization. If the Slack workspace you picked is already connected somewhere else, disconnect it there first. The reverse is allowed: one Bordio organization can have several Slack workspaces connected.

2. Connect your account (each person, for themselves)

Installing the app doesn’t tell Bordio which Slack user is you. Until you connect your own account, no direct messages are sent to you and Slack actions won’t work.

In Slack, run:

/bordio connect

Click the button in the reply, sign in to Bordio as usual — single sign-on and two-factor authentication both apply — and approve the connection. Bordio confirms in Slack, and the browser tab returns you to the app.

You can also start from a link preview: paste a Bordio link in a channel and, if you’re not connected yet, the bot offers you a connect button in a DM.

3. Add Bordio to the channels you work in

The first two steps already give you most of the integration: tasks can be created from anywhere in Slack, and Bordio links expand into cards in any conversation. Two things, though, need the app to be a member of the channel — posting into a private channel, and reading replies in a thread.

In the channel, run:

/invite @Bordio

Or open the channel’s Integrations tab and add the app there. Bordio posts a short confirmation, and from that moment everything works in that channel.

Here is what you get, depending on where you are:

Where you are	Task is created	Link previews	Card from `/bordio add`	Thread replies become comments
Public channel, app not added	Yes	Yes	Yes	No
Private channel, app not added	Yes	Yes	No — Bordio explains why	No
Any channel, app added	Yes	Yes	Yes	Yes
Direct or group message	Yes	Yes	No, and it cannot be fixed	No

Four things are worth knowing from this table.

Link previews don’t need the app in the channel. Bordio registers its own addresses with Slack, and Slack expands links to them anywhere in the workspace. This is the one part that works without any per-channel setup.

Replies in a thread do need it. Slack passes on messages only from conversations an app belongs to, so in a channel without Bordio a card can be sitting right there while replies under it go nowhere. Nothing warns you — the reply simply stays a Slack message.

A private channel hides itself from apps entirely. Until Bordio is invited, it cannot post there: the task from /bordio add is still created, and Bordio tells you — in that channel, visible only to you — that the card had nowhere to go.

Direct and group messages stay out of reach. Slack gives no way to add an app to someone else’s conversation, so cards from /bordio add never appear there and replies aren’t synced. Links still expand, and the task itself is created normally.

Permissions Bordio asks for

Permission	Why
Send messages, including to public channels	Personal notifications and replies to your commands
Open direct messages	Delivering those notifications to you
Read and write link previews	Expanding Bordio links into cards
Slash commands	`/bordio add`, `connect`, `disconnect`, `status`
Read messages in public and private channels	Syncing thread replies under a preview into task comments
Read basic profile information	Showing which Slack account is connected, and naming people mentioned in threads

Bordio doesn’t request access to your direct messages or group DMs, so threads there aren’t synced.

Bordio acts only on replies in threads under its own cards. Everything else in a channel is ignored: nothing is stored, and nothing reaches your tasks. In a channel where the app has not been added, Bordio isn’t told about messages at all.

Slash commands

Command	What it does
`/bordio connect`	Connect your Slack account to your Bordio account
`/bordio status`	Show whether your account is connected, and to whom
`/bordio disconnect`	Disconnect your account and stop personal messages
`/bordio add <text>`	Open a form to create a task, with the title pre-filled

Disconnecting

Your own account. Run /bordio disconnect in Slack, or open Profile settings → Integrations → Apps with access to Bordio in Bordio and revoke the Slack connection. Both do the same thing: personal messages stop, and Slack actions no longer work until you connect again. Nothing in your tasks or comments is removed.

The whole integration. In Organization settings → Integrations, disconnect the Slack workspace. Previews, notifications and commands stop for everyone in that Slack workspace. The integration can be connected again later.

Removing the Bordio app from the Slack side has the same effect: Bordio notices, marks the integration as having lost access, and offers to reconnect.

Notifications — choosing what reaches you
Tasks in Slack — previews, actions, creating tasks, threads
Troubleshooting — when something doesn’t show up