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

# Review and organize feedback

> Collect customer requests, review submissions, merge duplicates, and keep customer conversations together.

Use **Feedback** in the workspace dashboard to turn incoming customer requests into a clean, useful queue for product decisions.

## Collect a request

Customers can submit through the public portal or packaged widget when **Portal → Behavior → Requests** is set to **Collect feedback** and **Visitor accounts** is enabled. Customers must sign in before submitting. Follow the [quickstart](/quickstart) to verify that path.

To add feedback on a customer's behalf, select **New request** in **Feedback**. Choose the customer and board, enter a customer-readable title and detail, then select **Create request**.

<Check>
  The request is collected when its title appears in **Feedback** and opening it shows the expected
  requester.
</Check>

## Review new submissions

When request moderation is enabled, customer submissions arrive in **Pending** and stay out of public request lists until your team approves them.

Open a request, confirm that it is understandable and belongs in the selected feedback stream, then move it to **In Review**. Use **Closed** when your team will not pursue it. Later stages—**Planned**, **In Progress**, and **Completed**—connect the request to roadmap work.

Use the board, stage, and search filters to narrow the list. Sort by **Newest**, **Oldest**, **Top voted**, or **Most commented** when reviewing a larger queue.

<Check>
  An approved public request appears on the portal. A request in **Pending** or **Closed** remains
  available to your team but is absent from public request lists.
</Check>

## Summarize feedback with the assistant

Plus workspaces can ask the in-app assistant to summarize recent feedback. Open your avatar menu, select **Support**, then choose **Summarize this week's top requests** or ask for the feedback window you want to review.

The assistant reads only the feedback available to your signed-in workspace and returns its summary in the conversation. It does not edit, merge, moderate, or reprioritize requests for you.

## Organize requests with boards

Workspace owners and admins manage boards under **Workspace settings → Feedback**. Boards separate feedback by purpose or audience.

| Access          | Customer experience                                                   |
| --------------- | --------------------------------------------------------------------- |
| **Public**      | Any signed-in customer can submit; anyone can read approved requests. |
| **Private**     | Customers can submit and see only their own requests.                 |
| **Invite-only** | Only invited customers can access the board.                          |
| **Internal**    | Only workspace team members can access the board.                     |

Private, invite-only, and internal boards require a paid plan. Every workspace must keep at least one board.

Choose **Add board** to create another stream, or edit a board's name and access in place. For invite-only beta groups, manage customers and a linked roadmap item from the same board row.

## Merge duplicate requests

Open the request you do not want to keep, select **Merge request**, search for the request that should remain, and confirm **Merge request**.

Glean Feed moves votes and comments to the request you keep, then closes the duplicate. Read both requests before confirming; a merge changes the customer history attached to the surviving request.

<Check>
  The surviving request contains the combined demand, and the duplicate no longer appears as a
  separate active request.
</Check>

## Keep customer conversations attached

Open a request to read public comments, reply as your team, and add private notes. Private notes stay in the dashboard. Team replies can appear in the public conversation.

Use the **Comments** control on the request when a public thread should become read-only. Existing comments remain visible, but customers cannot add another comment.

Portal voting and comments require customer accounts and the matching controls under **Portal → Behavior**.

For Linear issue and project links, vote-threshold automation, and disconnect behavior, see [Connect Linear](/integrations/linear).