Skip to main content
A board is a set of charts you come back to. There are two kinds: ours, which we keep for every workspace, and yours, which hold what you pinned.

Where boards live in the app

Boards are part of the Scoreboard. Open the Scoreboard and press Boards next to its title, or type “boards” in the command palette (⌘K). The address is /scoreboard/boards.
  • The list shows ours first, then yours, with each board’s pin count and whether it has a live link. It says how many of your 50 boards you have used. Name a board under New board to make an empty one; it opens straight away.
  • A board (/scoreboard/boards/{id}) shows every pin asked now, each with its n. On a board of yours you can Rename it, Share it, Export CSV, Delete it, and Remove one pin. On ours you can export it, and nothing else.
  • After you pin a chart from a chat, the confirmation links to the board it went on (Open the board).
A board that reads a source this workspace has not connected says so once, above its pins, with a link to where you connect it: Set up AI traffic opens the Scoreboard’s AI traffic view (the install steps, or on Starter the card that switches plan), and Connect Search Console opens Customize → Connectors. A source that is not available on this deployment is named without a link, since there is nothing to connect.

A pin is a saved question, not a picture

When you pin a chart, the board stores the question that drew it: the metric, how it is grouped, the window and any topic or prompt it is filtered to, plus whether to draw it as a chart, a table or a single number. It never stores the numbers or an image of them. Every time the board opens, each pin’s question is asked again. A share of voice pinned on Monday shows Friday’s share of voice when you open the board on Friday, and it is the same figure the rest of the dashboard shows that day. The window behaves the way it was asked:
  • A pin asked over the last N days keeps reading the last N days, ending today.
  • A pin asked over fixed dates keeps reading those dates.

Ours and yours

Ours are defined by us, the same for every workspace, and never stored, so a better default reaches every workspace the day it ships. They are read-only: you can open and export them, and nothing else. To change one, pin the questions you care about to a board of your own. Unless a row says otherwise, a pin on our boards reads the last 30 days. A board whose source this workspace has not connected still opens. The pins that read that source say why they have nothing to show, rather than drawing an empty chart that looks like a zero. Yours are what you pinned. A workspace keeps up to 50 boards of its own, and each board holds up to 24 pins. Everyone in the workspace sees the same boards.

Pinning a chart

Pin to board sits under any chart, table or metric the agent draws in a chat by asking a question of your measurements. Press it, then pick one of your boards or make a new one; a new board is made and the pin goes on it. Only your own boards are offered, because ours take no pins. A board that already holds 24 pins cannot take another. Once it is pinned, Open the board takes you to it. A view that is not the answer to such a question, such as a summary the agent read, a draft or a card, has no question to keep, so it has no Pin control. When a pin names a topic or a prompt, the question is checked as you pin it. A topic or prompt that is not in this workspace is refused then, rather than shown broken every time the board opens. On your own boards you can also, from the board in the app or over the dashboard routes:
  • Rename the board.
  • Remove one pin.
  • Delete the board. Its pins go with it; they are only questions, and the data they read is untouched. Deleting a board also turns its link off.
Making a board, pinning, renaming and reordering are refused when the org’s credits are used up. Removing a pin, deleting a board, exporting, sharing and turning a link off always work.

Reading a pin

Every pin carries its n: how many observations its rows stand on, summed across the rows. Read it first, for the reasons in Reading the numbers.
  • A cell nobody measured is drawn as an em dash, never as 0. A 0 means we read the answers and the count was zero.
  • A pin with no rows in its window says “Nothing in this window yet.”
  • A pin that hit its row limit says how many rows it is showing.
  • Coverage gaps are named under the pin.
One pin failing never fails the board. A pin whose question could not be answered says so in its own place, and every other pin still shows its answer. A topic or prompt deleted after it was pinned is one way this happens.

Exporting a board

The export (export.csv, below) is the board as one table, with one line per row of every pin. Both our boards and yours export. Two rules carry over from the dashboard:
  • An unmeasured value is an empty cell, never 0, and its n is still written beside it, so “measured, none” and “not measured” stay apart in a spreadsheet too.
  • A pin with no answer is still a line, carrying its error, so the file never drops a pin the board showed as broken.
Text a spreadsheet would run as a formula, such as a prompt that starts with =, is written with a leading apostrophe so it opens as text.

Sharing a board with someone who has no account

Share on one of your boards makes a link (in the app, or over the API); Copy link copies it and Turn link off stops it. Anyone with the link can open the board without signing in. Our boards cannot be shared; pin what you need to a board of your own and share that.
  • The link lasts 180 days from when it was made. The shared page says until when.
  • Sharing again gives back the same link, so a second share never breaks the copy you already sent.
  • Turning the link off stops it at once. Whoever opens it after that is told the board’s owner turned it off. Your other shared links keep working: other boards, client reports and receipts.
  • After you turn a link off, sharing makes a new link with a fresh 180 days. The old one stays off.

What the reader sees

The board’s name, and each pin’s title, chart, numbers and n, drawn with no controls. Row labels are not hidden, so a pin grouped by prompt or page shows those prompts and pages; pin only what you are happy for the link’s holder to read. The reader does not see your workspace, your org, who made the board, or anything about cost or credits. The page is not indexed, and a pasted link previews only as “Shared board” and “A page shared with you.” A shared board’s reading is kept for 10 minutes: everyone who opens the link inside that window sees the same reading. A reading in which a pin could not be read on our side is not kept, so the next open asks again. Any change to the board, such as a pin added or removed or a rename, shows on the next open. If the link will not open, the page says which of these it is: Board links are signed with the same workspace secret as receipts, shared rewrites and client reports. Rotate on the receipt stops all of them together, board links included. To give a reader a working link again after a rotation, share the board again; the new link keeps the old one’s expiry date.

Over the API

Dashboard routes (signed-in session):
  • GET /v1/projects/{id}/boards: ours and yours, with the limits.
  • POST /v1/projects/{id}/boards with {"name": "..."} makes an empty board.
  • GET /v1/projects/{id}/boards/{boardId}: the board with every pin asked now. Each pin carries its table (columns, rows, n, unit, window and gaps) or its error. not_connected lists each source the board reads that this workspace has not connected.
  • PATCH /v1/projects/{id}/boards/{boardId} renames a board, or reorders its pins with pin_order and the pins_version you read it at. A reorder against a board someone else changed in the meantime is refused, so reload and reorder again.
  • DELETE /v1/projects/{id}/boards/{boardId} deletes a board and turns its link off.
  • POST /v1/projects/{id}/boards/{boardId}/pins with {title, query, view: {component: "chart" | "table" | "metric", props}} pins a question. query names a metric, up to two group_by dimensions, the window as days or as from and to, and any filters (topic_ids, prompt_ids, engines, country and the like), all at its top level. An unknown field is refused rather than ignored.
  • DELETE /v1/projects/{id}/boards/{boardId}/pins/{pinId} removes one pin.
  • GET /v1/projects/{id}/boards/{boardId}/export.csv: the CSV above.
  • POST /v1/projects/{id}/boards/{boardId}/share returns {token, url, issued_at, expires_at, expires_in_days}, the same link while one is live. DELETE on the same path turns it off.
Our boards are addressed by name (overview, engines, search, traffic), and any edit to one answers 405. Public route, where the token is the credential:
  • GET /v1/share/{token}: {kind: "board", board: {...}}, the shared board. A turned-off link answers 404; an expired or invalid one answers 401; a link opened too often answers 429.
Boards are not MCP tools.