Use your installation’s identity provider to sign in. There is no shipped default administrator or password. The operator configures login; your account menu links to this guide, notification settings, themes and logout.
Select an application or All Apps. Administrators add applications to an empty installation. Assignment team members and authenticated user roles are separate.
Search titles and descriptions; filter by application, type, status and assignment. Hot, Top and New sorts offer different views. Open a card for its votes, discussion, attachments, history and duplicate relationship.
Feature requests suggest improvements; bugs report unexpected behavior; critical reports flag blockers. Helpdesk tickets are private to their creator and staff. Internal notes are staff-only.
Workflow: Open, Investigating, Planned, In Progress, Shipped, Back Burner and Won’t Fix. A status is not a guaranteed delivery date.
1. Describe: select the application and type; explain the problem, reproduction steps and expected behavior.
2. Enhance (optional): review AI wording when OpenRouter is configured. Skip this step and keep your own text when AI is unavailable.
3. Check duplicates: contribute to a matching existing ticket where possible. The wizard’s text-based suggestions are not exhaustive semantic discovery.
4. Review: verify the description and optional attachments, then submit. New issues do not automatically add your vote. Storage is optional; manual submission works without it.
Use the up arrow to add or remove your own vote. Votes show interest, not a delivery promise. Comments help the team reproduce and understand issues; staff replies are labeled.
Locked tickets cannot receive member comments. Staff moderation can hide or lock content. Admins and superadmins may edit ticket titles and bodies; other edit controls depend on ownership and existing participation.
Use a private helpdesk ticket for sensitive support. Staff replies go to the creator; staff internal notes are separate. Never include credentials in any ticket or screenshot.
Follow a ticket for updates; per-ticket delivery preferences override global preferences. The notification bell shows unread in-app updates. Unfollow when updates are no longer useful.
Email is optional and requires Resend with a verified sender. Without email, in-app feedback still works. Helpdesk reply controls disclose email availability.
Mention preferences are reserved for future detection; typing @name is not a guaranteed notification. SMS is not included.
Google Cloud Storage supports JPEG, PNG, GIF, WebP and PDF files up to 10 MB. Uploads use signed URLs to a private bucket. File access checks ticket permissions and issues short-lived download links; treat those links as temporary bearer credentials.
Voice transcription requires optional OpenAI configuration, browser microphone permission and a compatible hosting request limit. You can always type instead.
Missing AI, storage or email providers show unavailable controls or setup messages. Manual browsing, submission, comments and votes do not need provider keys.
Members participate in feedback. Support, admin and superadmin can triage, assign, change workflow, review, hide, lock, reply, add internal notes and merge under staff rules.
Only admin and superadmin edit ticket titles and bodies or change applications, team and AI configuration. Login privileges remain database-controlled; the operator grants staff roles, never browser input.
Use the staff table or Kanban view to organize work. Merge an eligible duplicate into a canonical ticket; votes and watchers transfer without duplication.
Shipped tickets can produce changelog entries. Optional OpenRouter drafts reader-friendly text; without AI a plain fallback is used. Review public text before publishing.
Admin → AI Settings accepts an OpenRouter key and separate text/agent models. Recommended default: deepseek/deepseek-v4.1-flash. Optional OpenAI configuration enables voice transcription and semantic discovery of already indexed feedback.
Saved keys use AES-256-GCM with an independent deployment-owned encryption key. Without that key, credential persistence is disabled and the operator uses environment configuration. Keys are always masked.
Saved overrides take priority. Clearing an override returns to environment configuration; it does not erase an environment key. Save before testing; fixed official provider tests may consume small amounts of credits.
AI providers receive the necessary text or audio. The operator should review provider terms and inform users about data processing. AI settings do not enable Agent Native’s deployment flags.
The Agent button is available only to support, admin and superadmin when the operator enables a reachable sidecar. Desktop opens a dock beside the portal; mobile uses a full-height panel. Chat stores history and New thread starts another conversation.
Try: ‘Do we have feature requests for dark mode across applications?’ Ask for exact counts, an application breakdown, methodology and clickable source tickets.
Keyword queries cover titles, descriptions, comments and internal notes. Full exact counts are distinct from bounded displayed rows. Semantic candidates are related suggestions, not exhaustive counts; existing embeddings are required and coverage is disclosed.
‘Reply to all of those and mark them planned’ prepares an immutable preview of exact tickets, proposed text, changes and side effects. Preparing a proposal changes no feedback.
Inspect the preview in Approvals, then explicitly approve the durable execution prompt in Chat. Typing ‘yes’ is not approval. Writes and consequential execution also require the operator’s separate flags.
Bulk operations require a saved exact cohort of at most 200 tickets, bound to your account, portal and thread for one hour. Proposals expire after 30 minutes. Narrow larger cohorts. Changed tickets are skipped as stale and need a new preview.
Results show successes, stale skips, failures and notification warnings per target. Replay returns the original result without duplicate comments, events or emails. Interrupted or uncertain work needs operator reconciliation, not another automatic write.
The agent exposes five business actions: query, inspect one issue, list resources, prepare and execute approved feedback operations. It cannot delete tickets, manipulate member votes, manage configuration, reveal secrets, run code or deploy software. Logout revokes sidecar access.