Skip to content
Docsturbobase.io

Channels

Shipped

Channels connect your Turbobase instance to Slack, so it can reach your team where they already work. Slack is set up in one place — Settings → Slack — and is not one of the tiles in the Sources catalog.

Connecting your Slack workspace

Section titled “Connecting your Slack workspace”

An administrator opens Settings → Slack and clicks Add to Slack. Slack asks the workspace for every permission Turbobase uses in one consent screen; there are no extra permissions to grant later for individual features. Once the install finishes, the same page shows the connected workspace, whether Slack events are reaching your instance (with a retry if they are not), and when the last one arrived.

Turbobase works in the channels its bot has been invited to. Invite it with /invite @TurboBase in each channel you want it in. It keeps those channels — messages, thread replies, edits, deletions and members — up to date in real time, and Settings → Slack lists every channel with its sync status, a switch to stop syncing one, and Sync now. Messages is how many of that channel’s messages are in Turbobase right now, so it moves as messages arrive. Last synced is when the channel’s last complete pass through its history finished; the first pass can take days on a busy workspace, and until it finishes the column shows when the channel’s newest message landed instead — messages are already searchable long before the history is fully in.

Connected before this release? Click Add to Slack again. Turbobase now requests all of its Slack permissions at once, and Slack only grants new permissions when a workspace consents again. Until an administrator reinstalls, Settings → Slack shows a banner asking for it, and anything that needs a permission your workspace has not granted fails — nothing is switched off for you. Reinstalling keeps every setting on the page.

Disconnecting on Settings → Slack removes the bot token and every Slack setting from your instance. The Slack workspace stays registered to this Turbobase instance, so connecting the same workspace to a different Turbobase instance needs Turbobase support.

Asking Pilot from Slack

Section titled “Asking Pilot from Slack”

@-mention @TurboBase in any channel it has been invited to and your message goes to Pilot, your AI assistant, which answers in place. In a thread, Pilot reads the whole thread first, so a follow-up question does not need to repeat what was already said.

Every question runs as you: the answer is scoped to your own role and row-level security. If you have not linked your Slack account yet, Turbobase replies privately with a pointer to the Account page — your account menu, or /settings/account — instead of answering.

Asking from Slack works whether or not the web chat is switched on — the pilot-chat setting decides whether Pilot appears in the Turbobase app, not whether it answers here.

While the web chat is on, the reply links to the conversation in Turbobase for administrators, and everyone else sees a note that viewing it there is admin-only at the moment. While it is off, the reply says neither: there is no conversation to open.

Direct messages are off unless an administrator turns them on on Settings → Slack. Until then, a direct message to the bot gets no reply; @-mentions in a channel work either way.

Making changes from Slack

Section titled “Making changes from Slack”

When a question leads to a change — posting a message, creating or renaming a channel, updating a canvas, changing a record — Pilot posts what it proposes to do and waits. The person who asked confirms by reacting with ✅ (or replying confirm) and cancels with ❌ (or cancel). A reaction from anyone else does nothing, and a proposal nobody answers expires.

Administrators choose which kinds of Slack action Pilot may take — posting, reactions, channel management, canvases and files — on Settings → Slack. Channel management is admin-only whatever the setting.

Who can see what

Section titled “Who can see what”

Pilot only uses Slack content the person asking is allowed to see.

Who is asking Slack content Pilot can use
Someone who has not linked their Slack account Public channels only
Someone who has linked their Slack account Public channels, plus the private channels and group DMs their Slack user is a member of
An administrator Every channel Turbobase syncs

An answer posted in a Slack channel is visible to everyone in that channel, so it never draws on a different private channel — only public channels and the channel you asked in. In a direct message with the bot, your normal access applies.

Linking your Slack account

Section titled “Linking your Slack account”

Every user links their own Slack account on the Account page — your account menu, or /settings/account — under Connected accounts. Linking is what lets Pilot answer your questions from Slack, lets a notification @-mention you, and lets you see the private channels you belong to.

An administrator can also onboard a teammate channel-first: a channel invite from /admin/users/invite carries a one-shot token, and redeeming it creates the Turbobase account and binds the chat identity in a single step.

Outbound notifications

Section titled “Outbound notifications”

Your instance can post a notification into the Slack channel an administrator picks on Settings → Slack and @-mention the right person — for example when a scheduled task has something for someone to look at. Messages render in Slack’s native format (mrkdwn).

Section titled “Related”