Assistant in Slack

The assistant is the same one you talk to in the dashboard — same data, same tools, same limits. Slack is a second place to reach it, so you can ask about a page in the channel where someone just complained about it.

There are two ways to talk to it:

• Direct message. Send the Kitbase app a DM. Everything you say there is one running conversation, so you can follow up without repeating yourself.
• Mention it in a channel. Invite the app to a channel and start a message with @Kitbase. Each thread is its own conversation — two people can ask about different things in the same channel without the answers getting tangled.

It only answers when it is spoken to. In a channel it reads nothing it was not mentioned in.

It can never do more than you can

Every answer and every action runs as your Kitbase account, checked against your own permissions at the moment it runs. Someone who cannot delete a brand in the dashboard cannot get the assistant to delete one for them in Slack either.

Setting it up

1. Connect the workspace

An organization admin connects Slack once, from the Slack integration in your Kitbase settings. That is the same connection used for notifications, so if you already have Slack connected you are most of the way there.

If your workspace was connected before the assistant existed, reconnect it — the assistant needs permission to receive messages, and an older connection was never granted it. Notifications keep working either way.

The connection asks for these bot scopes:

Scope	Why
app_mentions:read	See messages that mention the app in a channel
im:history	See direct messages sent to the app
chat:write	Post and edit its answers
users:read	Show who approved an action, by name
channels:read, channels:join, groups:read	Post notifications into channels

2. Link your Kitbase account

The first time you talk to the assistant it will not know who you are, and will send you a private link. Open it while signed in to Kitbase and confirm — that is what tells us which account is yours.

The link is deliberately one-way: it never says who you are in Kitbase, so a link that someone else sees can only ever connect their account to their Slack user. It expires in ten minutes and works once.

If you belong to more than one organization that has connected the same workspace, you will be asked which one you are acting for. That choice decides whose data the assistant reads when you speak to it — to change it, unlink your Slack account in your Kitbase account settings and link again.

3. Choose a project

Every answer is about one project, so the first time you talk to the assistant in a new place it asks which one:

• In a channel, the choice sticks for everyone in it — so it takes permission to manage the organization's integrations. Admins can see and remove channel bindings alongside the Slack integration in your Kitbase settings.
• In a DM, the choice is your own and needs no special permission.

To point a channel somewhere else, an admin removes the binding and the assistant asks again.

Approving actions

Most things the assistant does are read-only and simply happen. Anything destructive — deleting a brand, prompt, topic or webhook, cancelling a run, renaming a project — stops and asks:

Update project

{"name":"Docs site"}

Approve Deny

A few things about that prompt worth knowing:

• Only the person who asked can answer it. In a channel the buttons are in front of everybody, but a colleague pressing Approve would have the action run as your account, with your permissions and your name against it. So it will not let them.
• It waits for all of them. If the assistant wants to do two things, both get a prompt and nothing runs until both are answered.
• Denying is a real answer. The assistant is told you said no, and carries on from there — usually by suggesting something else.
• A decided prompt loses its buttons, so nothing can run twice.
• It waits as long as it takes. You can approve something the next morning; the request survives restarts and deploys. After a week it expires and you ask again.

While a decision is outstanding the assistant will not take a new message in that conversation — answer the prompt and it carries on.

What answers look like

The assistant posts one message and edits it as it works, so a long answer shows its progress instead of arriving all at once. Tables come through as code blocks, which is the only way Slack keeps their columns lined up.

If something goes wrong — a rate limit, a spend cap, a tool that failed — it says so in the same message, with what it managed to do first.

Limits

• No slash commands. Talk to it in a DM or mention it.
• It cannot read files you attach in Slack. Use the dashboard assistant for those.
• It does not read channel history. Each question stands on its own, plus whatever was said to the assistant earlier in that DM or thread.
• One turn at a time per conversation. A second message while it is still working gets a "one moment" rather than a second answer.