> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Portal Overview

> Public feedback boards, a roadmap, and a changelog your customers can read — connected to the feedback you already collect

The Portal is BuildBetter's customer-facing surface. It gives the people who use your product one public place to ask for something, watch it get built, and read about it when it ships.

Unlike a standalone feedback tool, Portal posts connect back to the requests BuildBetter already extracts from your calls, tickets, and conversations — so a public board reflects everything you know, not only what customers thought to post themselves.

## Boards

Everything in the Portal is a **board**. Each board has a kind, a name, a URL slug, and a visibility setting.

| Field              | What it does                                              |
| ------------------ | --------------------------------------------------------- |
| **Kind**           | `feedback` for idea boards, `changelog` for release feeds |
| **Name**           | Display name customers see                                |
| **Slug**           | The board's URL segment                                   |
| **Visibility**     | `public` or restricted                                    |
| **Status columns** | Roadmap columns, on feedback boards                       |
| **Disabled**       | Hides a board without deleting it                         |

You can run several boards at once. A typical setup keeps one feedback board for ideas and a separate changelog board per product line, so a mobile release doesn't clutter the main feed.

<Info>
  Boards are managed through the [MCP tools](../MCP/tool-reference) or the Portal settings in the app. Creating, updating, and deleting boards, posts, and voters are all available programmatically.
</Info>

## The Two Board Kinds

<CardGroup cols={2}>
  <Card title="Feedback boards" icon="thumbs-up" href="./boards-and-voting">
    Customers post ideas and vote. You see who asked, how many wait, and which accounts are behind each request.
  </Card>

  <Card title="Changelog boards" icon="megaphone" href="./changelog">
    Publish what shipped, with labels, and embed the feed in your own product.
  </Card>
</CardGroup>

A feedback board can also carry **status columns** — the public roadmap. See [Roadmap](./roadmap).

## How It Connects

The Portal is not a silo. Three connections matter:

* **Post matching** — portal posts are matched against feature requests already extracted from your other sources, so duplicates collapse into one item with all its evidence.
* **Voters** — every vote records the person and company behind it, which feeds the demand picture you use to prioritize.
* **[Releases / Close the Loop](../Success/close-the-loop)** — when something ships, BuildBetter matches it back to everyone who asked and drafts the message telling them. Publishing a changelog entry and telling the individual customer are separate jobs; the Portal does the first, Close the Loop does the second.

## Next

<CardGroup cols={2}>
  <Card title="Boards & Voting" icon="thumbs-up" href="./boards-and-voting">
    Running feedback boards, posts, statuses, and voters.
  </Card>

  <Card title="Roadmap" icon="map" href="./roadmap">
    Planned, In Progress, and Shipped columns.
  </Card>

  <Card title="Changelog" icon="megaphone" href="./changelog">
    Publishing entries and embedding the feed.
  </Card>

  <Card title="Close the Loop" icon="rotate" href="../Success/close-the-loop">
    Telling the customers who asked.
  </Card>
</CardGroup>