Skip to content
Integrations
Sign inEarly access
All integrations

Biddle for Slack: a daily team briefing by DM

Biddle is a Slack app. It reads the channels you invite it to, sends the leader a briefing by DM each weekday morning, posts a team recap in its own #askbiddle channel, and answers when someone asks it a question. This page lists every Slack scope it asks for at install and what each one does.

Last updated

At a glance

Install
Add to Slack, through Slack’s own OAuth screen. Biddle asks for the 19 bot scopes below and refuses an install that is missing a required one.
Reads
Channels it has been invited to, public or private, plus DMs sent to it.
Posts
DMs, its own #askbiddle channel, and threads where someone asks it.
Keeps
Raw Slack messages for 90 days. The decisions and workstreams it derives stay until you remove your organization.
Status
Early access. Free during early access.
On this page

The Slack scopes Biddle asks for

Slack shows this list on the install screen. 11 scopes read and 8 write. The write scopes cover posting messages and charts, opening DMs, running one channel of Biddle’s own, marking a question as seen, and previewing links to Biddle’s dashboard.

Bot token scopes requested at install
ScopeAccessWhat Biddle uses it for
channels:historyReadMessages and threads in public channels it has been invited to. They feed the record of decisions, the briefing, and answers.
groups:historyReadThe same for private channels it has been invited to. What it reads there shows up only in that channel or in a DM with someone who can see the channel.
im:historyReadMessages people send to Biddle directly: questions, corrections, and “stop”. It cannot read DMs between people, and it drops group DMs.
channels:readReadWhich public channels it is in and who their members are, so an answer cites only channels the asker can see. Also whether a channel is shared with another workspace.
groups:readReadThe same membership check for private channels.
app_mentions:readReadSeeing @Biddle when someone mentions it in a channel.
reactions:readReadEmoji reactions. Only a reaction on one of Biddle’s own messages is used, as feedback on that message.
users:readReadMember names, time zones, and account type. Time zones set when a briefing arrives, and account type tells members from guests and people outside the workspace.
users:read.emailReadFinding the Slack account that matches the email on a GitHub commit or a Linear user, so work is credited to the right person.
files:readReadOpening an image posted in the conversation where someone asks Biddle a question. At most 4 images per question, read for that one answer and never stored.
links:readReadSeeing a link to Biddle’s own dashboard (askbiddle.ai/app) posted in a channel it is in, so it can preview it. Other links are ignored. Asked for only once link previews are on.
chat:writeWritePosting briefings, answers, setup messages, and the team recap in #askbiddle.
im:writeWriteOpening a DM with the leader and with people the leader gave a seat.
channels:manageWriteCreating the public #askbiddle channel, setting its purpose, and inviting the leader to it.
channels:joinWriteJoining #askbiddle if a channel with that name already exists, and rejoining it if Biddle was removed.
pins:writeWritePinning the intro message in #askbiddle.
reactions:writeWritePutting an eyes reaction on a question while Biddle works on it, then swapping it for a check mark once the reply is posted.
files:writeWriteUploading a chart image Biddle drew into the conversation an answer or a scheduled post is in, right after it. Nothing else is uploaded, shared or deleted.
links:writeWriteAttaching a preview card to a Biddle dashboard link someone posted. Asked for only once link previews are on.

Signing in to Biddle’s web app is separate from the install. It uses Sign in with Slack, which asks the person signing in for openid, profile, and email.

files:read was added on October 9, 2026. A workspace that installed Biddle before then is answered from text until an admin reinstalls it.

What Biddle reads in Slack

  • Messages, threads, and reactions in the channels it has been invited to. When it joins a channel it also reads back the last four weeks of that channel.
  • DMs that people send to Biddle.
  • Member profiles: Slack user ID, name, display name and handle, title, time zone, locale, account type, and email address.
  • Images in the conversation where a question is asked: the question’s own message, its thread, or the messages just before it. They are downloaded for that answer and dropped with it.

What it never reads

  • DMs between people. Group DMs are dropped before anything is stored.
  • Channels it has not been invited to. Biddle does not join channels by itself. The one exception is its own #askbiddle.
  • Files in the background. It does not list or index your workspace’s files. An image is opened only when it sits in the conversation where someone asked a question.

Where Biddle posts

The leader’s briefing arrives as a DM on weekdays, from 9:00 AM in the leader’s Slack time zone.

A team recap goes to #askbiddle, a public channel Biddle creates for itself. That recap uses only GitHub and public channels, so anyone in the workspace can read it.

Answers go in the thread where someone mentioned @Biddle, or in the DM where they asked.

Each teammate with a seat gets their own morning note as a DM. It does not post in your other channels. Nudges between briefings are still being tested on our own team and are not sent yet.

Set up Biddle in Slack

Biddle is in early access, and we set each team up with you. The steps are the same ones Biddle shows in its Home tab.

  1. Request early access

    Sign in with Slack on the early access form and send the request. Once it is approved, the same page shows an Add to Slack button.

  2. Approve the install

    Slack shows the scope list above. The person who installs Biddle becomes its leader: the one who gets the morning briefing and manages connections.

  3. Connect GitHub

    Biddle sends a welcome DM with three steps and keeps the same checklist in its Home tab. The first is installing Biddle’s GitHub App on the account your team ships from.

  4. Invite Biddle to your product channels

    Type /invite @Biddle in each channel it should read. It reads nothing until it is in a channel.

  5. Choose seats

    Pick the teammates who get a seat. You can skip this and come back to it later.

Your first briefing arrives once Biddle has read what you connected. It does not wait for the next morning.

What Slack adds to the briefing

Slack is where your team decides things, and those decisions rarely make it into a PR description. Biddle keeps each decision and open question it finds in a thread, tied to the message it came from. In the briefing that turns into lines like the ones below: a question that has gone days without a call, or a decision the team made on Tuesday.

Sample data. The people, products, and threads are made up. In a real briefing the blue text links to the Slack thread.

Thursday

BiddleAPP9:00 AM

Onboarding moved since your last briefing. One call is yours today.

Needs you

  • Onboarding: SMS or email first for sign-in codes? The #onboarding thread has 7 replies and no call since Tuesday. Priya is holding the copy until someone decides.

Since last briefing

  • Checkout: The team agreed to keep the old receipt email through the holiday freeze, decided Wednesday in #checkout.

Pause or remove Biddle

To stop your own DMs, send Biddle the word “stop”. “Resume” turns them back on, and the Home tab has the same switch. You can still ask it questions while paused.

To stop it reading one channel, remove Biddle from that channel the way you would remove any member.

To remove it entirely, uninstall Biddle from your workspace’s app settings in Slack. Biddle stops all processing for the workspace at once, and everything it stored for your organization is deleted within 30 days. Deleted data can remain in encrypted backups for up to 5 days before it is overwritten.

Questions about Biddle and Slack

Does Biddle read every Slack channel?
No. It reads only the channels someone has invited it to, plus DMs sent to it. It cannot read DMs between people, and it does not join channels by itself, apart from its own #askbiddle channel.
Can a private channel’s content leak into a public answer?
No. An answer in a channel uses only that channel and the public channels the asker can see. Content from a private channel shows up only in that same channel or in a DM with someone who can see it.
Why does Biddle ask for files:read?
So it can look at an image when someone asks about one, such as a mockup posted in the thread. It opens at most 4 images per question, only from the conversation the question was asked in, and it never stores them.
Does Biddle post in our channels?
Only in its own #askbiddle channel and in threads where someone asks it a question. The leader’s briefing is a DM.
What happens to our data if we uninstall Biddle from Slack?
Biddle stops processing for the workspace as soon as Slack reports the uninstall. Everything stored for your organization is deleted within 30 days.

Related

Want this in your Slack?

Biddle reads your GitHub and Slack and sends you a briefing each weekday morning, with every claim linked to the PR or thread behind it. We’re onboarding a few product teams now, and we set each one up with you.

Request early access