Feedback

Feedback is the operational intake channel for both user product signal and automated security probes.

Feedback intake and surfaces

Alumia separates feedback into two streams:

• feedback — user reports and signal observations attached to project/session context when available.
• notifications — system notices like schedule failures, usage warnings, and subscription changes.

Both streams are accessible from:

• /<orgSlug>/feedback for submitters to review their own threads
• /admin/feedback for operator review
• the in-chat /feedback command — /feedback <message> submits straight away, while a bare /feedback opens the composer
• Feedback API for programmatic submit/list (/api/v1/feedback)
• /api/v1/admin/feedback for operator retrieval and status updates

Security probe filtering

The admin feedback surface can group and inspect common probe families:

• script / injection probes (<script>, javascript: and event handlers)
• command-style probes (sleep, id, shell-like patterns)
• SQL-style probes (UNION SELECT, conditional numeric comparisons)
• template injection patterns
• path traversal probes (../, absolute system paths)
• fuzz patterns (common test-noise payloads)

Administrators can filter by signal family and escalate only the meaningful items.

Workflow states and actions

Feedback items support explicit workflow states and handoff metadata:

• Status: open, triaged, in_progress, done, archived
• Handoff: none, build, build/bugfix flow control
• Automation controls for routing repetitive reports into follow-up tasks
• notes and action timestamps with safe HTML output

This allows the same route to act as bug triage, security triage, and feature request intake in one place.

Signal quality and noise handling

The pipeline computes quality labels at ingest time:

• low_signal
• short_actionable
• actionable
• security_probe

In noisy periods, duplicate and burst groups can be surfaced together so triagers do not process identical submissions repeatedly.

Why this matters

The feedback surface is part of product reliability, not just support chat:

• it catches repeated probe patterns before they become incidents,
• highlights real product issues separately from synthetic test traffic,
• and gives operators concrete state transitions so nothing gets silently dropped.

How to submit feedback

Use the feedback button in the dashboard (📝 icon in the top bar) and include:

• a short title in the first line,
• the steps to reproduce, with the route or session you were on,
• what you saw versus what you expected,
• and the impact (who is affected and how).

The submission attaches your current route, viewport, and session context automatically, so you do not need to paste those by hand.

After you submit

Shared-canvas visitors on /share/project/[token] can open the feedback popover; submissions attach route, session, and canvas context automatically for admin triage.

The admin feedback queue prioritizes signal items first — verified issues get a direct reply with the fix tracking status, typically within one business week.

For coordinated security disclosures involving third parties, contact the security address listed on the public site.