Skip to main content
Channels let your team ask Hive questions where they already talk. Mention @Hive in a channel or send it a direct message in Slack or Microsoft Teams, and Hive answers in the thread using what it knows about your business. Open Integrations → Channels: “Ask Hive from Slack or Microsoft Teams. Signals and approvals stay in Hive.”

What channels do — and don’t

Channels are conversation only, apart from the Slack direct messages below. Hive answers only Hive members: in a channel or a direct message, Hive answers only when the sender’s Slack or Teams email matches a member of your Hive workspace. Answers in a channel run with read-only, answer-only access. See Who Hive answers. Signals, approvals and actions stay inside the Hive app, where roles and audit apply. An answer that cites sources ends with a line such as Sources: Stripe · Brain · Signals. It uses the same labels as the Sources in the Hive app. A connector’s name means a live read made for that answer; stored Business Brain knowledge, saved rules, detected signals and drafts waiting for approval are labelled Brain, Memory, Signals and Pending approval. Channel answers never propose actions, so they never carry the Your request label. See Citations. A link in an answer shows its full address in brackets after its words, for example pricing page (https://example.com/pricing), so you can see where it goes before you click it. Hive’s answers in the web app show links the same way (see Keeping AI output honest). In Teams, a link whose address Teams might show differently from where it goes (a host that is not plain letters, digits, dots, hyphens and underscores, or an address holding an HTML entity such as &) shows only its words, with no link. In Slack and Teams alike, a link whose address carries a username or password shows only its words. In Slack, messages from Hive show no link previews: Slack does not fetch or expand the links in an answer or a direct message from Hive.
Channels are different from the Slack and Microsoft Teams connectors, which let Hive read messages and post. See Email and calendar.
When an agent or a workflow posts to Slack through the connector (Post message, Reply in thread, or a channel or direct message Hive sends for it), an @here, @channel, @everyone or user-group ping in text an AI wrote shows as plain text, and a link shows its address, so nobody is pinged by text an AI wrote. A workflow step whose message is fixed text, with no {{…}} value, keeps its pings. Mentions of a person and links to a channel still work, and a post you approve on an Ask or Signals card is sent as you approved it. A Slack message or direct message that Ask or Signals sends by itself from an Act account, with no one approving it, gets the same treatment: its pings and disguised links show as plain text.

Supported platforms

Each Slack workspace or Teams tenant can be connected to exactly one Hive workspace. Only Owners and Admins can install or disconnect a channel.

Install in Slack

1

Start the install

In Integrations → Channels, choose Slack and start the install.
2

Approve in Slack

Slack shows the permissions Hive’s bot requests. Approve them for your workspace.
3

Invite and ask

Invite @Hive to a channel, or open a DM with it, and ask a question.
The bot requests these Slack scopes: Hive does not request chat:write.public, so it cannot post to channels it has not been invited to. Bot tokens are encrypted in Hive’s vault.

Direct messages from Hive in Slack

When your workspace has Slack installed, Hive sends two kinds of direct message to members:
  • Connection alerts, when one of your connected accounts stops working, with a link to reconnect it. See Connection alerts.
  • Billing notices, to Owners and Admins, and to a member a seat change is about: your trial ending or ended, an offer, a payment problem, a read-only or cancelled workspace, usage alerts, and a seat suspended over the plan’s limit, moved to another seat type or given back. The messages to Owners and Admins say to open Settings → Billing. Usage alerts and seat changes follow your Usage alerts and Seat changes switches in Settings → Notifications; the other billing notices can’t be muted.
Hive finds each member in Slack by their Hive sign-in email, so a member whose Slack address is different gets no direct message. A workspace that installed Slack before these messages existed must reinstall the Slack app to grant users:read, users:read.email and im:write. Until then, no connection alert can reach its members. Teams direct messages are not available yet.

Who Hive answers

Hive matches each person who messages it to a Hive account by email, and nothing else:
  • The email comes from the chat platform’s own directory: in Slack, the email on the sender’s member profile; in Microsoft Teams, the sender’s Microsoft 365 sign-in name (user principal name), which must be on a domain your tenant has verified. Hive does not use the separate Microsoft 365 Email field, because an administrator can set it to any address.
  • It must match, ignoring letter case, the sign-in email of exactly one current member of the Hive workspace the app is installed in. Hive only looks in that workspace, never in any other.
  • Hive checks on every message. If you leave the Hive workspace, or your email changes so the two no longer match, Hive stops answering you as a member straight away.
There is nothing to link or confirm. Guests, bots, and people from another company’s Slack workspace or Microsoft 365 tenant (for example in a Slack Connect channel) are never treated as members. When Hive does not answer, its reply says why:
  • You hold no seat in the Hive workspace. Hive answers nothing for you, and acts on no approval or denial you send, until an Owner or Admin gives you a Basic, Pro or Max seat on the Members page.
  • You are on an Approver seat. Hive replies as it does to a member without a seat: an Approver seat includes no Hive answers in Slack or Teams. Open the items routed to you in the Hive app, where you can ask Hive about them. An Owner or Admin can give you a Pro seat for open Ask.
  • No Hive account matches your email. Ask a workspace admin to invite you to Hive with the same email you use in Slack or Teams.
  • The Slack app can’t read email addresses. The workspace installed Hive before it asked for users:read.email. A workspace admin must reinstall Hive for Slack from Integrations → Channels. Until then, Hive answers no one in that workspace.
Each answer is an Ask turn and uses credits like one in the Hive app: on Business, the asking member’s own AI credits. On Business there is no daily limit on answers in Slack and Teams. On an earlier plan, a short channel answer typically uses about 4 credits, and each member on a Pro or Max seat can get a limited number of Hive answers in Slack and Teams a day: 50 on Starter and 300 on Team (days in UTC). Past that, Hive replies that you have reached today’s answers in Slack and Teams, and you can keep asking in the Hive app. A member without a seat gets no answers, in Slack and Teams or anywhere else, and neither does a member on an Approver seat: Hive replies that they need a seat, as it does to a member without one, and counts nothing. On Business, a member who has used their credits and any extra usage the workspace allows gets a reply that says so. On an earlier plan, if your workspace is out of credits or has too few left for a full answer, you have reached your own monthly credit limit, or a payment is overdue, a member on a Pro or Max seat still gets their quick answers (10 a day and 200 a month), in a direct message with Hive or in a channel or thread. These are short answers on an Efficient model, without web search, and use no credits. Once the quick answers are used, Hive replies with the reason. In a read-only workspace Hive replies with the reason straight away. Connection alerts and billing notices that Hive sends you as Slack direct messages use no credits. See Billing and plans. Settings → Slack and Teams shows the Hive sign-in email your chat account has to match. If the AI model Hive uses is busy or unavailable when you ask, Hive replies that the model is busy or unavailable right now and to ask again shortly, rather than with a general error. If no AI model is configured for your workspace, Hive says so and asks you to have a workspace admin check Hive’s model settings, since asking again would not help.
Hive used to link chat accounts with a one-time link you confirmed in Hive. Those links are gone. Existing links were revoked on 2 October 2026, and old link pages do nothing.

Install in Microsoft Teams

1

Start the install

In Integrations → Channels, choose Microsoft Teams and start the install. You sign in with Microsoft and grant consent for your tenant.
2

Check your Microsoft role

The person installing must hold one of these Microsoft Entra roles: Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator. Teams Administrator alone is not enough.
3

Add the app in Teams

Install the Hive app from Teams so people can find it, then @mention it or send it a chat.
Hive requests only openid and profile at sign-in and no resource-specific permissions. Organization.Read.All is optional and only used to show your tenant’s name. To match a sender to a Hive member, Hive reads that sender’s sign-in name from the conversation’s member list through the Teams bot service, which needs no extra permission.

Statuses

Disconnect

Disconnect the installation from Integrations → Channels. For Teams, this revokes Hive’s installation, but the app and consent on the Microsoft side stay until a Microsoft administrator removes them.

Ask Hive

What Hive can answer.

Roles and permissions

Who can manage channels.