Using Biddle

Add Biddle to a new workspace

• Biddle is in early access. Request access at askbiddle.ai: sign in with Slack, then tell us your team size, what you are building and your GitHub organization, and press Request early access. Once your workspace is approved, the same place shows an Add to Slack button.
• Add to Slack opens Slack's own install screen. It lists the Slack permissions Biddle asks for (each one is explained on the Slack integration page), and Biddle installs nothing if a required one is missing. The person who installs becomes the leader: they get the leader briefing and manage Biddle for the workspace. The workspace's time zone and language start from their Slack profile.
• Biddle then DMs the leader a welcome with three steps. 1) Connect GitHub: Install Biddle on GitHub adds a read-only GitHub App and lets you pick the repos. Only the leader or a workspace admin can do this; if your GitHub organization needs an owner to approve apps, Biddle waits for that approval. 2) Invite Biddle to the channels it should read: type /invite @Biddle in each one. 3) Choose seats for teammates (optional; Just me for now is fine).
• Right after the install Biddle creates its own channel for the team post (#askbiddle by default) and reads the last 4 weeks of the channels it is in.
• The first briefing does not wait for the next morning: it arrives in the leader's DM 10 to 70 minutes after Biddle finishes reading. If there is nothing to report yet, Biddle says so and the regular briefing starts the next weekday morning.
• The Get your first briefing checklist on Biddle's Home tab in Slack shows what is left. Only the leader and workspace admins see it, and it disappears when every step is done.
• Then connect the other tools your team uses (see Connect your tools) and add seats for the teammates who should get their own morning note.

Request early accessBiddle for Slack: scopes and setup

Connect your tools

• GitHub and Slack are the core: GitHub with Install Biddle on GitHub in the welcome DM or the Get your first briefing checklist on the Home tab (the leader or an admin), Slack by inviting Biddle to channels. Connect GitHub in Home > Your settings only links your own GitHub account.
• Every other team tool is connected once for the whole team by the leader or a workspace admin, in Slack > Biddle > Home > Connections (or dashboard Settings > Connections): press Connect next to the tool. Biddle only ever reads from them. The list there shows each tool's status and which ones are not available yet.
• After connecting, choose what Biddle reads where the tool asks (the Figma folders, the Google Analytics properties, the ad accounts, the Stripe products): Manage on the same row. Reconnect appears when a connection needs it, and Sync now pulls fresh data.
• A few tools take a read-only key you create and paste instead of a sign-in: Stripe (a restricted key), Meta Ads (a system user token while Biddle's Meta app review is pending), Sentry (an auth token) and PostHog (a personal API key). The setup guides walk through each screen.
• Ramp (company spend) connects with a sign-in to Ramp by someone who is a Ramp Admin or Business Owner. Biddle reads card transactions, bills and reimbursements (about 13 months back, then every two hours) and answers spend questions for full members in DMs and channels not shared with another workspace; Who can use it on the same row narrows that.
• Gmail is personal: each member with a seat connects their own in Slack > Biddle > Home > Your settings > Your connections, and Biddle reads it only in that person's own DM and morning note. An admin can limit connecting your own tools to the leader and admins in dashboard Settings > Permissions.
• Where custom connectors are on, the leader or an admin can also add a read-only MCP server: Slack > Biddle > Home > Connections > Custom connectors > Add custom connector.
• Disconnect on the same row deletes what Biddle stored from that tool. Workstreams and decisions it already wrote stay. A metrics tool (Google Analytics, Search Console, Meta Ads, Google Ads, PostHog) is the exception: its numbers are hidden for 30 days and come back if you connect the same account again, unless you choose Delete the numbers now.

All integrationsConnect Meta Ads with a system user tokenConnect Stripe with a restricted key

Briefings

• The leader gets a briefing by DM each weekday morning, with the team stand-up (9:00 by default in the workspace's time zone, not the leader's own): what needs a decision, what changed since the last briefing, and what is worth a look. Every line links to the pull request or message it came from.
• Each teammate with a seat gets a morning note about their own work: what changed, what waits on them.
• The team post goes to #askbiddle: a daily stand-up, and a product briefing weekly on Monday or daily in the stand-up (leader or admin: Home > Team > Product briefing). The leader or an admin can turn the team post off for the workspace in dashboard Settings > Team rules.
• Reply in a briefing's thread to ask a follow-up or correct a line in plain words ("that shipped last week"). With a seat, the correction fixes the team record for everyone; reply "undo" to put it back. Starting a reply with "Correction:" keeps a standing instruction for your own briefings.
• Change the time, days, language or content of your briefing in Settings (below).

Your settings: What Biddle knows about you

Nudges

• Between briefings Biddle can DM a teammate with a seat when something needs them: a pull request waiting on their review, a question waiting on their decision, a teammate's unanswered mention, something they said they would do that is past its date, a merged pull request that drifts from a decision, checks failing on their pull request, or a sharp move in a connected number (ad spend, conversions, traffic, search clicks).
• At most 2 nudges a day, and one of each kind.
• Stop one kind with Stop next to it in Slack > Biddle > Home > Your settings > Nudges (Resume turns it back on). To pause every DM from Biddle, see Settings.
• Nudges are switched on per workspace by the Biddle team (not a setting in Slack or the dashboard), and new kinds are tested before they are sent.

Ask Biddle

• DM Biddle, @mention it in any channel it is in, or reply in a thread where it answered (no mention needed for 7 days after its last reply there). In Biddle's shared channel, just ask: no mention needed.
• Ask what you would ask a teammate who read everything: how a product is going, what changed this week, who is working on what, what was decided and why, what a pull request or the code does, and, with the tools connected, the numbers (traffic, ads, revenue, errors) as a table or chart.
• An answer uses only what the person asking can see: the channels they are in and the tools connected for them. In a channel, it uses what that channel can see. Numbers from connected tools are read in a DM or a channel not shared with another workspace.
• Biddle answers in the language you ask in and links the sources it used.
• If an answer is wrong, say so in the thread; Biddle re-checks the original and corrects itself. With a seat, a correction also fixes the team record for everyone.

Pages and apps

• A live page keeps an answer up to date: a teammate with a seat asks Biddle in a DM (or a channel not shared with another workspace) to make a page of the numbers you want; an admin can limit making pages to the leader and admins in dashboard Settings > Permissions. The figures are read fresh each time someone opens it, with that person's access. Find them in the dashboard under Pages.
• An app is a small tool Biddle builds for the team, such as a tracker or a form: a teammate with a seat asks for one in a DM, a channel not shared with another workspace, or the dashboard. Find them under Apps; an app's data and code can be exported from its page.
• Pages and apps are switched on per workspace by the Biddle team (not a setting in Slack or the dashboard).

PagesApps

Scheduled posts

• Ask in plain words: "every Monday at 9, post last week's ad numbers in #marketing". Biddle proposes the schedule and you confirm it with a button.
• Where the workspace has event posts on, a post can also follow an event: "when a pull request merges, summarize it in #release".
• Ask Biddle to list, pause, change or delete them, or use Scheduled in the dashboard: each post's runs, cost, and Pause, Resume and Delete.
• Scheduled posts are made in a DM or a channel not shared with another workspace. They are switched on per workspace by the Biddle team, not by a setting in Slack or the dashboard. Where they are on, an admin can limit creating them to the leader and admins in dashboard Settings > Permissions.

Scheduled

The dashboard

• The dashboard is at askbiddle.ai/app. Sign in with Slack; you see only what you can see in Slack. It needs a seat: without one you can still ask Biddle in Slack.
• Today (Overview in some workspaces): what needs you and the latest briefings. Products (or Board): each product or workstream, what is moving and what waits on a call. Decisions: decisions and open questions. People (or My view): what each teammate owns and what waits on them. Search: Biddle's record.
• Scheduled, Pages and Apps list what Biddle posts and built; Journal and Customers (support themes) appear where the workspace has them on.
• What Biddle knows about you (askbiddle.ai/app/me/knows): your notes, your briefing preferences, the team rules and your corrections; edit or delete any of them.
• Usage shows AI spend (the leader and admins, and members when an admin allows it in Settings > Permissions). Settings has Account and Team rules for everyone, and for the leader and admins Workspace, Products and channels, Connections, People, #askbiddle, Permissions, Billing and Audit.

DashboardWhat Biddle knows about you

Settings

• Pause Biddle's DMs to you (morning notes, watches, nudges): DM it the single word stop (or pause, 그만, 멈춰, 중지). resume (or start, 재개, 다시) turns them back on. The same switch is Pause DMs in Slack > Biddle > Home > Your settings. Questions still work while DMs are paused.
• Briefing time and days: ask Biddle ("send my briefing at 8") where the workspace has chat settings on, or set them in the dashboard on What Biddle knows about you. Whole hours from 6:00 to 20:00 local, on weekdays. The leader or an admin sets the workspace default in dashboard Settings > Team rules.
• Briefing language: ask Biddle ("brief me in Korean"), or Home > Your settings > Briefing language. Questions are answered in the language you ask in.
• Leave products or areas out of your briefings by asking Biddle, where the workspace has chat settings on; What Biddle knows about you lists what you left out (Reset puts one back) and takes a style request. The leader or an admin sets the team's style request and turns the team post off in dashboard Settings > Team rules.
• Stop one kind of nudge: Stop next to it in Home > Your settings > Nudges.
• Stop Biddle reading a channel: remove it from that channel (/remove @Biddle). It reads only channels it is in.
• The workspace's time zone: dashboard Settings > Workspace (the leader or an admin).

What Biddle knows about you

People, seats and permissions

• The leader is the person who installed Biddle (the leader or an admin moves it with Home > Team > Change leader, or Transfer leader in dashboard Settings > People). The leader gets the leader briefing and is the base seat.
• Admins manage Biddle for the workspace (connections, seats, settings): the leader, the people made admin in dashboard Settings > People, and Slack workspace admins and owners.
• A seat means Biddle may message that person first (the morning note, nudges). The leader or an admin adds seats in Home > Team > Manage seats (or Add seat next to an active teammate), or in dashboard Settings > People. Each seat beyond the leader will be billed.
• Members without a seat can still ask Biddle anything in Slack; the dashboard needs a seat. Guests and people from other workspaces cannot hold a seat.
• Who sees what: an answer uses only what the person asking can see, so a private channel's content stays with its members. Settings > Permissions (an admin) sets whether members can create scheduled posts and pages, connect their own tools and see usage, who Biddle messages first, how it answers in channels shared with another workspace, and whether it answers guests. It does not switch features on: which features a workspace has is set by the Biddle team.

Privacy and data handling

• The Data handling page says exactly what Biddle reads, never reads, keeps and for how long, sends to AI models, and how to delete it. Biddle gives the same answers when you ask it in Slack.
• Your own notes and preferences are on What Biddle knows about you, where you can edit or delete them.

Data handlingPrivacy PolicyTerms

Pricing

• Free during early access. Paid plans will be a flat team price with low-cost extra seats, and you’ll see the price before you’re ever charged.
• The leader and admins (and members, when an admin allows it in Settings > Permissions) can see what Biddle spends on AI for the workspace under Usage in the dashboard.

Questions on askbiddle.ai

Remove Biddle

• From one channel: /remove @Biddle in that channel. Biddle stops reading it.
• One tool: Disconnect in Slack > Biddle > Home > Connections deletes what Biddle stored from it. A metrics tool's numbers are hidden for 30 days first; delete them sooner with Delete the numbers now, or under Settings > Connections > Hidden numbers.
• From the workspace: remove the Biddle app in Slack's app settings. Biddle deletes everything it stored for the workspace 7 days after the uninstall by default, and always within 30 days; reinstalling before then cancels the deletion.

Data handling