> ## 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.

# Collect your first customer request

> Create a workspace, prepare its public portal, and confirm that customer feedback reaches your dashboard.

This quickstart takes you from a new Glean Feed workspace to one request submitted through the public portal and visible to your team. You do not need to install code or connect another tool.

## 1. Create a workspace

Sign in and choose **Create workspace**. If this is your first workspace, Glean Feed opens this form during onboarding. Otherwise, open the workspace switcher at the top of the dashboard sidebar and choose **Create workspace**.

Enter the **Workspace name** for the product or brand collecting feedback. Review the generated **Workspace URL**; this becomes part of the public portal address. **Website** is optional and lets Glean Feed look for a logo, favicon, and description during setup.

Select **Create workspace**. Glean Feed opens the workspace dashboard and creates two starting boards: **Feature Requests** and **Bug Reports**.

## 2. Confirm the feedback board

A board groups related customer requests. For this first loop, use **Feature Requests** so customers have an obvious place to share product ideas.

Open your avatar menu, choose **Workspace settings**, and select **Feedback** under Product. In **Boards**, confirm that **Feature Requests** is set to **Public**. Public means anyone can submit and read approved requests.

You can rename the board if another label will make more sense to your customers. Keep at least one public board available for this quickstart.

## 3. Make the portal ready to collect

The portal is the customer-facing site for this workspace. In workspace settings, select **Portal**, then open the **Behavior** tab.

Under **Public sections**, set **Requests** to **Collect feedback**. This is the mode that lets customers submit new requests. Under **Visitor actions**, keep **Visitor accounts** enabled; accounts are required for submissions and interactions.

Save the behavior settings. Roadmap and Updates can stay on or off—the first feedback loop only depends on Requests.

## 4. Open and share the portal

Return to the dashboard and select **Public Portal** in the sidebar. It opens the customer portal in a new tab. Confirm that the portal shows a way to share feedback and that **Feature Requests** appears as a board.

To copy the customer-facing URL, return to **Workspace settings → Portal → Share**. Use **Copy** beside **Public portal URL**, then send that link to a customer or open it in a private browser window for this test.

## 5. Submit one request

On the portal, choose the prompt to share feedback. If prompted, create or sign in to a visitor account. In the **Share feedback** dialog:

1. Choose **Feature Requests**.
2. Enter a **Short title** that describes one real customer need.
3. Add useful detail under **What should change?**
4. Select **Submit**.

If your workspace moderates new submissions, the request can wait for team approval before other customers see it. It should still reach the dashboard immediately.

## 6. Confirm the request reached your team

Return to the workspace dashboard and select **Feedback** in the sidebar. Find the title you just submitted.

<Check>
  The feedback loop is working when the submitted title appears in **Feedback** and opening it shows
  the expected requester. If moderation is enabled, seeing it in **Pending** is the expected result.
</Check>

Open the request to review its description and customer. Your team can now approve it, add context, merge duplicates, or move it through the product process.

## Build on the working loop

Choose the next step that matches how your team wants to collect or act on feedback:

* Refine the [portal experience](/portal/overview) before sharing it more widely.
* Learn the full [feedback review workflow](/dashboard/feedback).
* Add the [packaged widget](/widget/install) to collect feedback inside your product.
* Connect an assistant through [MCP](/api/mcp) or build a custom workflow with the [API](/api/overview).
* Connect [Linear](/integrations/linear), add a [custom domain](/portal/custom-domains), or explore the [Headless SDK](/headless/overview) when the basic loop is established.