@helyx/module-feedback

Feedback lets server members send bounded public feedback cards to a manager-selected Discord channel, either from a slash command or a reusable dashboard-published panel.

Availability and deployment

Feedback is Live and supported by Hosted Helyx and Helyx Self-Hosted. It uses Helyx runtime and Discord capabilities only and requires no external provider credentials.

What it does

Managers choose the destination and whether public cards show the member's display name. They can also publish a persistent button panel. Members submit a short subject and message through a private modal; the completed card is public. Feedback is not a private support-ticket system and does not retain the submitted text outside Discord.

Commands and interactions

| Path or control | Default access | Purpose | | ---------------------- | -------------- | ---------------------------------------------- | | /submit feedback | Everyone | Open the bounded feedback modal. | | Feedback panel button | Everyone | Open the same feedback modal. | | Dashboard post-panel | Manage Server | Publish a reusable panel in its saved channel. |

Submission attempts are limited to three per member per hour, with an additional short command reservation. The modal explains public visibility, identity handling, and sensitive-data guidance before submission.

The slash command is controlled by feedback.send. Completing either modal is controlled separately by the open-by-default feedback.participate operation, so narrowing the slash command does not silently disable an allowed panel role. The command route must satisfy both policies; the panel route checks only the participant operation before applying the normal submission rules.

Dashboard configuration

Managers select the public destination channel, public attribution mode, optional panel channel, panel heading, panel guidance, and button label. Posting a panel is a separate authorised action after settings are saved. If required panel metadata cannot be stored, Helyx removes the new Discord message instead of leaving an unmanaged panel.

Discord requirements

Helyx needs View Channel and Send Messages in the configured feedback and panel channels. The module does not require Administrator, Message Content, or a privileged gateway intent.

Data, privacy and retention

feedback_submissions retains a generated submission ID, server, destination channel, Discord message ID, nullable submitting account ID, public attribution mode, and timestamp. feedback_panels retains panel ownership metadata and a nullable creating account ID. Privacy access and erasure use the registered provider even when the module is disabled; erasure can detach those account IDs. The subject and feedback body remain in Discord and follow Discord and server retention controls.

Operational audit and optional customer activity records contain bounded identifiers and settings, never the submitted subject or message. Disabling Feedback stops ordinary commands and dashboard actions but preserves retained records until an explicit deletion process applies.

Operations and failure behavior

Helyx validates and normalises settings and modal values at the bot boundary. A public feedback card is removed if its required metadata cannot be stored. Failed audit, achievement, or optional Logging delivery does not reverse a durable submission or a published panel. Health reports stopped state, missing required services, recent delivery failure, and degraded secondary-event delivery without exposing raw exception messages.

Documentation and support

See the Feedback guide, commands, permissions, troubleshooting, and FAQ.