Dashboards are rolling out gradually: if the Dashboards page in your workspace says they are coming soon, they have not reached you yet and everything below describes what arrives when they do. Dashboards are live views over your connected tools, shared with exactly the people you choose. Example: a delivery dashboard showing the team's overdue ClickUp tasks next to open and due-this-week counts, so the Monday standup starts from the same live numbers Binee also uses when you ask about a slipping client date in chat.
Creating a dashboard
Workspace owners and admins create dashboards from the Dashboards page in the sidebar. New dashboard opens a template gallery: pick a ready-made dashboard (for example the Delivery board, or My Binee brief with your latest Binee findings next to your task activity) and one click creates it with its cards already computing from your own data, choose Blank dashboard to name one and add cards yourself, or choose Build with AI to describe the dashboard to Binee in your own words. The gallery normally offers only the templates your connected tools can fill, and tool-specific templates appear as their tools are connected; if the connection check cannot load for a moment, everything is shown rather than hiding real options. The same templates and the Build with AI tile also sit at the bottom of the Dashboards page. Build with AI opens Binee Assistant with a starter you complete, like "Build me a dashboard that tracks my team's meetings and client emails"; Binee designs a small coherent set of cards for the subject (a trend chart or two, a headline number, a list of what needs attention), shows the whole proposal on one confirmation card, and one confirm creates it. Asking in chat directly works the same way: "build me a dashboard to track my team's sales activity" gets a designed proposal, and if you ask for changes, the revised proposal replaces the earlier version of the same proposal - that older confirmation card is cancelled automatically. An unrelated proposal you have not confirmed yet stays open until you confirm or cancel it, and a cancelled or already-handled card always refuses politely instead of acting twice. Cards can be added to an existing dashboard the same way (see Cards below). Every member sees the Dashboards page, with the dashboards they created or were invited to, each entry showing its cards, how many people see it, and when it last changed. To jump between dashboards, click the dashboard's name at the top of the page: a menu lists every dashboard you can see, plus New dashboard for owners and admins.
The Pulse
Every dashboard opens with its Pulse, a section pinned above the cards where all of Binee's thinking about the board lives. It carries three things: a status pill for the whole board (Looking steady, Worth a look, or Needs attention), a short written update on what the numbers say about the business, and up to three ranked findings where Binee connected dots across the board's cards and sources. Each finding carries an importance label (High means act now, Medium means look soon, Watch means keep an eye on it), a matching colored edge, and the logos of the tools it drew from. Example: the cards show completed tasks dipping and meetings piling up, and the Pulse's top finding connects the two - the dip lines up with three days of back-to-back client escalation calls.
The Pulse reads the cards themselves: each card's current numbers are its primary material, so a board of ten delivery cards gets a delivery read and a mixed board gets cross-tool connections. It also learns what this board's readers value: every member (viewers included) can mark a finding useful or not useful with the thumbs on it, and the next refresh's Pulse leans toward what the team found useful. Voting the same way again removes your vote; dismissing stays separate and just means handled. Example: mark the client-risk findings useful and the routine volume notes not useful, and within a few refreshes the Pulse leads with client risk.
The Pulse is written once per refresh, from the same evidence the cards are computed from. Its ClickUp reading follows the board creator's own visibility, private spaces included, the same consent rule as cards that read a creator's live tools: putting a board in front of teammates is choosing to share what it reads. When something limits what the evidence covers, the Pulse says what it could not see instead of presenting a gap as a quiet business. It can be collapsed from the arrow in its corner when you want the numbers full-screen (each viewer's choice, remembered on their device), and editors can dismiss a finding once it is handled - dismissing hides it for everyone on the dashboard. A new dashboard shows the Pulse empty until the first refresh writes it. There is no separate button for it: the dashboard's one refresh recomputes the cards and the Pulse together.
Cards
A card is one live view on the dashboard. The fastest way to add one is to just say it: open Binee Assistant while looking at the dashboard and describe what you want to see, in your own words - "I want a daily chart of how many meetings and emails I get". Things you describe together become ONE card: that request is a single chart with a line for meetings and a line for emails, reading only the tools you actually have connected (and when two of your connected tools could mean the same thing, Binee asks which one you mean). The confirmation shows a small preview of each card - its name, its shape, and the tool logos it reads, plus a note when a named tool is not connected yet - and one confirm puts it on the board, where it appears immediately and starts computing. Said anywhere else in chat, Binee asks which dashboard the card should go to, or offers to build a new one. The Add card button offers three paths:
Create a card: describe what to track in plain words, for example "how many meetings I have each day", pick the sources it reads, pick its shape or let Binee choose, and optionally name it. A card reading several tools draws one line per tool with a legend, for example meetings and calls per day on one chart; when one of its tools cannot produce day counts, the card says so and draws the ones that can. A number that comes from a capped reading shows as "15+" rather than pretending to be an exact total; where the tool offers a true count (a mailbox's total, meetings per day, emails received per day), the card shows the exact number. Binee works out how to compute it once, and from then on every refresh fills the card with real computed numbers: a headline figure for the card's time range, the change against the matching previous period (for example "vs previous 7d"), and a chart of the underlying days where the data has them. Binee is always available as a source, and every connected tool appears as its own equal chip - pick which ones the card reads. Tools are pulled with the card creator's own connection at each refresh. A card can also put the board's ClickUp task series and a live tool's events on one chart: asking for the correlation between completed tasks and meetings draws tasks closed per day and meetings per day as two lines together, so you can see whether they move together - Binee reads requests like that as "show these side by side", the way a person means them, never as a statistics assignment to refuse. If you ask for something its sources cannot produce as numbers at all (judgment calls, text analysis, data the tool does not expose), Binee normally says so before the card is created: in chat it explains why and proposes the closest card it can compute, and in Card settings the save is refused with the reason. In the rare case one slips through (a momentary model failure at creation), the card says exactly what cannot be computed after its first refresh - either way, it never shows made-up numbers. If a live source cannot answer something at refresh time (a plan limit, missing history), the card says so too.
Start from a template: ready-made cards filterable by source (each shows its logo) and by shape. Beyond the built-in set, every connected tool with an honest ready-made offer has its own templates - for example Emails waiting on me for your mailbox, Upcoming meetings for your calendar, Recently updated files for your file tools, Unpaid invoices where you run billing, and Upcoming court dates where a legal practice tool is connected. There are also cross-tool templates that only Binee can draw, like Tasks and meetings per day, which puts your completed tasks and your recorded meetings on one chart, one line each; a cross-tool template appears once every tool it reads is connected. Clicking a template shows a small confirmation window first (so a stray click never creates anything); confirming adds it as a card of your own that starts computing immediately.
Build with AI: hands the whole thing to Binee Assistant with a starter you complete in your own words, like "completed tasks and client emails per day, one line each"; Binee designs the card, shows it on one confirmation, and one confirm puts it on the board. Nothing is sent until you press send.
The dashboard header shows logo chips for the tools its cards read from, and each card carries its own source logos, so you always see where the numbers come from. The built-in templates are:
Overdue ClickUp tasks: the most overdue open tasks, oldest first, with how many days each has slipped.
ClickUp task counts: open tasks, overdue, and due this week.
Completed ClickUp tasks: how many tasks finished in the last 7 days (Closed and Done-type statuses both count), the change against the week before, and a daily trend line over two weeks.
Workload by assignee: open tasks per teammate, with how many of each person's are overdue. Unassigned work gets its own row.
Progress by list: open and overdue counts per list, busiest first.
Needs your attention: your latest Binee insights with severity and age, and a See all link to the Insights page. Example: a slipping ClickUp date connected to a promise made by email shows up here next to your delivery numbers.
Binee automation activity: your Binee automations, when each last fired, and how many insights each produced this week.
Created through Binee: of the tasks created in the time window, how many Binee created from chat or your Binee automations, with Binee's share. Counting starts from when this card shipped.
The Binee cards show your own insights and automations, so each viewer sees their personal feed there, never a teammate's, and they re-pull quietly each time the dashboard is opened. The ClickUp cards show the board's latest ClickUp numbers (see ClickUp numbers below), and each card's time stamp says how old they are; created cards follow the refresh schedule below.
Every card has an ask button (the speech bubble on it) that opens Binee Assistant with a matching question already typed, for example "which of my overdue tasks are most urgent, and is any of them breaking a date we promised a client?". Nothing is sent until you press send, so you can edit the question first. Editors get one Card settings button (the sliders on the card) that opens everything editable about that card in one place: its name and category, what it tracks and its shape (on created cards), its time range, and its filters (on ClickUp cards: space, list, assignee, rows shown) - each card shows the settings its type supports, and double-clicking a card's name opens the same settings. Card names always show in full on the card, wrapping to more lines when a card is narrow. The three dots menu holds just Hide card and Remove. Changing what a card tracks rebuilds just that card right away. Shape and time range are free display changes that apply the moment you save, never a recomputation: the shape picker offers exactly the shapes this card's data can wear (the way every report tool works), so a daily count can become a line, bars, a pie, a list, a table, or one total number, and a single number can become a one-row list - each switch redraws on the spot. A card still computing, or an older summary-only card, applies your pick when it next computes, and says so on the card. A card that counts dated things (tasks completed per day, meetings per day) also redraws its numbers, headline, and change instantly for any range the last refresh covered - refreshes deliberately gather more days than the card currently shows, so switching between the common ranges like 7, 14, and 30 days redraws on the spot. A range past what the last refresh gathered applies at the next refresh and the card says so. When a created card cannot answer, it offers Build this card with Binee, which opens Binee Assistant with the card and its problem prefilled so Binee helps you rephrase it or pick better sources. Hiding keeps the card and its setup but takes it off the board (and out of refresh costs) until an editor shows it again from the Hidden cards row at the bottom; viewers never see hidden cards. The category is the short label like Finance or Delivery in small caps above the card's title, so a big dashboard reads in sections: template cards arrive with a fitting one already set, Binee sets one on cards it designs when the area is clear (a meetings-and-emails chart lands under Communication), and Card settings adds or changes it any time.
Time ranges
The board range switcher in the dashboard header is the one time range for the whole board: pick last 7 days (the default), 14, 30, 90 days, or last year, and every period card redraws to that range at once, free. A card can be pinned to its own range instead: in its filter editor, Time range offers "Dashboard range (default)" or a pinned range, and a pinned card wears a small pin marker with its range (for example a pin and "30d") so a card ignoring the board switcher always reads as intentional, never as a bug - say, a quarterly total pinned on a board everyone else reads weekly. Refreshing while the board shows a wide range gathers that whole span, up to a full year of daily data where the card's tools can truly count it (for example meetings per day); a tool that can only verify a shorter span says exactly which days its chart covers. Cards that show the current state, like overdue tasks, have no range and their own wording says what they cover.
Editors can filter a card from the sliders button: ClickUp cards narrow to one space, one list, or one teammate's tasks; Needs your attention sets how many rows it shows; period cards set their own time range. Example: a "Delivery overview" dashboard with the overdue card filtered to the Delivery space and the counts filtered to one client's list. Filters narrow what the card counts, within the dashboard creator's ClickUp visibility; the filter choices list the spaces, teammates, and lists (those holding open or recent tasks) in the board's latest ClickUp numbers. Editors arrange the dashboard directly: grab any card by its title bar and drop it wherever you want on the grid, and resize it from its corner or edges. Number cards can be sized down to a compact tile; chart cards keep a larger minimum so their axes stay readable. Cards adapt to the size you choose: charts grow to fill the card, a number card's figure scales up with a bigger card, long lists scroll inside their card. Other cards flow around the one you are moving and everything settles into a tidy structure when you drop; the layout saves for everyone immediately, and an Undo chip appears in case the drop was not what you meant. There is no practical limit on how many cards a dashboard holds (a generous safety cap exists so a runaway script cannot flood a board).
Sharing and who sees what
Sharing is per dashboard, and it is the one place where seeing is decided: a dashboard is either just yours, or shared, and shared means every member sees everything on it, now and as cards are added. The creator invites workspace members as viewers (they see the dashboard) or editors (they can also add, remove, and rearrange cards and invite viewers), and can change anyone's role in place from the share window at any time; the share window says plainly what adding someone means before you add them. Only the creator can rename or delete the dashboard, grant the editor role, or remove members. Only invited people and the creator see a dashboard; being an admin does not reveal other people's dashboards.
Everyone on a dashboard sees the same numbers. Cards that read a connected tool use the connection of the person who put them there, and ClickUp cards use the dashboard creator's ClickUp connection, private spaces they belong to included - adding a teammate to the board shares what its cards show, and the share window says so before anyone is added.
ClickUp numbers
A dashboard's ClickUp numbers come from Binee reading the dashboard creator's ClickUp with their own connection, working the numbers out, and keeping only what the board displays: counts per list and per teammate, daily completed and created counts for the last 90 days, and the task names an overdue card shows. The tasks themselves are not stored. Binee updates these numbers about every 4 hours on its own. Pressing refresh on the dashboard updates them sooner whenever they are more than 10 minutes old, and adding or re-filtering an overdue card starts an update that usually lands within 15 minutes. A very large ClickUp workspace can take longer to finish an update, and until it does the cards keep showing the previous numbers. Each ClickUp card's time stamp shows when its numbers were taken, so a card reading "3h ago" means ClickUp as it was three hours ago; ask Binee in chat for anything you need as of right now. Example: the Delivery board's overdue card shows what was overdue at the last update, and asking Binee "what is overdue for Maria right now?" reads ClickUp live.
ClickUp day counts go back 90 days: a ClickUp card set to a longer range (last year, say) counts or draws the last 90 days and says so on the card. A card filtered to a space or teammate that is not in the creator's ClickUp says so instead of showing zeros. If the creator's ClickUp connection stops working, the cards keep the last numbers and say the latest update failed, and a brand-new board shows a short "computing" note until its first update finishes, usually within 15 minutes. If the board's creator leaves the workspace, its ClickUp cards say so and show nothing. A board whose creator has not connected ClickUp shows an honest note on its ClickUp cards instead of empty numbers pretending to be zero. Keeping these numbers current costs no credits on its own.
Cards that read your own tools
A card reading live sources (your mailbox, calendar, meeting recorder) is computed with your own connection - a teammate's card never reads your tools, and yours never read theirs. Who sees the numbers is simply the dashboard's membership: on a dashboard only you can see, only you see them; on a shared dashboard, everyone on it does, because you chose to put the card there. Example: your "Emails waiting on me" card on the team's delivery dashboard shows everyone the same list, computed from your inbox.
For a scheduled recap of your work delivered to Slack or email, use a Binee automation; a dashboard is the live view, and automations are the delivery channel. Example: "every Friday morning, send the delivery status to the client channel" as a Binee automation.
Refreshing and cost
Opening a dashboard reads numbers Binee already holds and costs no credits, and that stays true no matter how often anyone opens it. The Binee cards re-pull free on every open, the ClickUp cards read the board's latest ClickUp numbers for free, and every filter, time range, board range, and shape change is free too - browsing and adjusting a dashboard never spends anything.
A refresh is the one thing that costs credits, and it works like a chat question: a refresh costs 0.5 credits, and when its gathering is heavy (pulling several of the creator's live tools, long histories), it is priced like the chat question it replaces, which can cost more - the exact charge shows on the workspace's Billing page. Each refresh recomputes every created card from its sources and writes the dashboard's Pulse in the same run. Refreshes are lazy: when someone opens the dashboard and the last refresh is more than 6 hours old, one refresh runs for everyone (never in the background, so a dashboard nobody opens spends nothing), and the Refresh data button in the header reruns it on demand, as often as you like. Pressing it again within a couple of minutes of a finished refresh shows a note that the numbers are already current instead of running a second paid refresh (that short pause only absorbs double clicks).
A card you create starts computing the moment you add it - it never waits for the next scheduled refresh, and that first computation covers just the new card at the cost of its own gathering, so adding one never re-buys the numbers the dashboard already has. The dashboard page itself shows no prices - this page and your Billing page are where the costs live, and you can always ask Binee what your credits were spent on. If the workspace runs out of credits, created cards simply stop refreshing and honestly show how old their numbers are; nothing else on the dashboard is affected. The same honesty applies when a refresh attempt fails for any other reason: the affected cards say so and retry on the next refresh, and anything already computed stays visible instead of going blank.