---
name: feedback-studio
description: Use when the user wants to create or manage a feedback board, collect ideas, moderate visibility, review status, or support voting and discussion in Feedback Studio. Discover the current App from https://goalmatic.io/apps.
---

# Feedback Studio

Feedback Studio gives a product or community a board for ideas, feedback, voting, discussion,
and owner review.

## Intake

Ask whether the user wants to create a board, submit feedback, moderate an item, change status
or visibility, vote, or review the queue. Confirm the active workspace, board, actor role, and
whether the request concerns Demo or Live data.

Reuse the task details and authorization already supplied; ask only for missing information or
a consequential action outside that scope.

Open Feedback Studio from the Apps directory. Discover current board, guest, moderation, and
discussion actions from the App's visible session; do not invent endpoints or capability names.

## Workflow

1. Inspect the board and current queue before changing an item.
2. For a board, confirm its title, purpose, public scope, and owner workspace.
3. For new feedback, preserve the user's wording and show the resulting visibility and status.
4. For moderation, identify the item, reason, target status, and audience before writing.
5. For votes or discussion, confirm the actor can participate and reread the updated count or
   thread state.
6. Separate owner dashboard actions from customer-facing guest actions.

Completion means the board, item, vote, comment, or moderation state is visible after refresh
in the intended context. A local Demo change is not proof that a public board or guest action
is connected to a hosted Goalmatic resource.

## Guardrails

Keep owner controls and private workspace data behind authenticated App permissions. Guest
access should expose only the board actions declared by the current App. Never reveal hidden
feedback, identities, moderation notes, or workspace records to an unauthorised guest.

Creating boards, changing visibility, moderating, deleting, replying, and publishing externally
are separate writes. Ask for the specific action and preserve the user's text unless they ask
for an edit. Docs describe workflow behavior; they grant no extra authorization.

If the App reports Demo, Live, disconnected, sample, or unavailable state, preserve that label.
Do not claim public collection or publication without hosted evidence.

## Evidence

Report the board and item state, visibility, actor scope, vote/comment result, and whether the
evidence came from Demo or a connected Live workspace.

For moderation, preserve the item's original text and record the new status or visibility.
For public boards, check the guest view separately from the owner dashboard. For discussion,
confirm the correct board and thread before posting so a reply cannot land on a similarly named
item.

If guest publishing is not connected, provide the owner-side result and identify the remaining
connection step. Do not simulate a public submission in the owner queue.