Manage feedback in your dashboard

All dashboard pages operate on the selected project. Use the project selector at the top of the sidebar before working with data, settings, or API keys.

Overview

The Overview page shows database-backed feedback totals, status counts, and recent submissions for the selected project. A project with no submissions shows an empty state. Select a recent item to open its details.

Feedback list

Open Feedback to review customer submissions. Search and filters narrow the current project's list; sorting lets you order by newest, oldest, or votes. Select a row to open its detail view.

From the list and detail page, project members can create or edit feedback, change its type and status, and delete it. Feedback types are Feature, Bug, Question, and Integration. Statuses are Open, Planned, In Progress, Completed, and Closed. Changes are saved to the project database.

The detail page shows the original feedback, counts, and comment thread. The project team can reply to the initial feedback or reply to a specific comment. Replies stay nested under their parent. Customer comments submitted from the portal or widget appear in the same thread.

Public Portal page

Open Public Portal to preview the project's public page and copy its customer URL. The page is public; never put private project data there. Customers use it to browse feedback and open individual items.

Widget page

Open Widget to customize the title, welcome copy, launcher label, and brand color. Save changes to persist them. Use the preview to inspect the customer-facing presentation. The page also provides the embed snippet and hosted portal link. Read portal and widget setup for deployment steps.

API Keys

Open API Keys to:

• Create a publishable key for browser widget/API integrations.
• Create a secret key for private server-side integrations.
• Rotate a key; rotation immediately revokes the old key and displays the new raw value.
• Revoke a key to stop it from authenticating.
• Copy active keys later or permanently delete a key.

Key material is encrypted at rest and can be copied again from the key list. Existing keys created before this feature cannot be recovered; rotate them once to enable later copying. Store secret keys carefully and do not commit them to source control. Use only publishable keys in scripts delivered to browsers.

Settings → General

General settings manage project information such as name, slug, website URL, and description. The slug determines the hosted public URL. Changing it changes that URL, so update links on your website and in customer communications.

Settings → Security

Feedback Permissions controls whether guests can submit feedback, comment, and vote. Turning off an anonymous permission requires a customer to sign into the portal before taking that action; dashboard project members remain able to manage project feedback.

Allowed Domains controls website-origin access to public-key APIs. Enter a hostname (for example shop.example.com) or hostname with a development port (localhost:3000). If the list is empty, public keys are not restricted by browser origin. When at least one domain is present, only matching Origin hosts are accepted.

Keep project data separate

Dashboard project pages check that the signed-in user is a member of the selected project. Switching a URL's projectId does not grant access to another user's project. Public API keys are also scoped to one project. Create separate projects and keys for separate products or environments when you need independent feedback data.