How Users Submit Feedback
The experience users have when submitting feedback to your portal.
How Users Submit Feedback
When users visit your portal, they can easily submit new feedback. Here's what the experience looks like.
The Submission Flow
- User clicks "Submit Feedback" — A button on your portal
- User signs in (if not already) — Via email, Google, or GitHub
- User fills out the form:
- Title — A short summary of their idea
- Description — Details, context, and use cases
- Board — Which board to submit to (if you have multiple)
- User submits — The post appears on your portal immediately
What Users Can Include
Title
A brief, descriptive title for the request. Encourage users to be specific:
- ✅ "Add dark mode to the mobile app"
- ❌ "Dark mode"
Description
Users can write detailed descriptions using rich text:
- Bold and italic text
- Bullet points and numbered lists
- Links to examples or references
Good descriptions include:
- What they want
- Why they need it
- How they'd use it
After Submission
Once submitted, the post:
- Appears on your public portal immediately
- Shows up in your admin inbox
- Starts with the default "Open" status
- Has 1 vote (the author's)
The user who submitted it automatically becomes a subscriber and gets notified when the status changes.
Editing Submissions
Users can edit their own posts after submission. This helps them:
- Fix typos
- Add more context
- Clarify based on team questions
You can control this in Portal Settings.
Submission Permissions
By default, users must sign in to submit feedback. You can configure:
- Authentication required — Users must sign in (recommended)
- Which sign-in methods — Email, Google, GitHub
See Portal Authentication for details.
Preventing Duplicates
Before submitting, encourage users to search for existing feedback. Voting on existing posts is more valuable than creating duplicates.
If duplicates come in, you can:
- Change the status to "Closed" with a note
- Link to the original post in a comment
Next: Learn about voting