Step 1
Read or draft a moderated comment
- Open the item's detail screen
- Read the existing discussion
Open a community item and read its existing discussion before adding a comment.
Our discussion and actions are synthetic. No comment is posted to the live board by this demonstration.
Step 2
Write a constructive comment
- Use the composer at the bottom
- Stay focused on the selected item
Use the composer at the bottom for a respectful comment focused on this item. Comments can contain one to two thousand characters.
Do not include account numbers, transactions, passwords, logs, device identifiers or sensitive personal details.
Step 3
Typing is not sending
- Review your wording first
- Choose Send only when ready
Typing a comment does not submit it. Review your wording, then choose Send only when you are ready.
This composer is separate from the Submit tab's locally saved idea or bug draft. Do not assume it is a durable backup.
Step 4
Received comments still need moderation
- Read the received status
- Pending comments are not instantly public
A received new comment starts awaiting moderation. It is visible only to you and the development team until approved.
Approval and the parent item's visibility determine public access. A successful Send does not promise instant publication.
Step 5
Confirmation clears the composer
- Check the empty composer after receipt
- Do not submit a duplicate copy
After confirmation, the original composer clears and the received comment appears with its moderation state.
Do not paste the same message again because it is not yet public. That waiting state is deliberate.
Step 6
Uncertainty keeps the exact comment
- Read Not confirmed and Retry
- Editing stays frozen until the result is known
If the response is lost, the server may already have your comment. The page retains its exact text and request identity.
The editor stays frozen, and Retry sends that same comment. Do not invent a fresh duplicate to work around the uncertainty.
Step 7
The preserved retry creates one comment
- Retry when the service is reachable
- Check one received comment and a cleared composer
Our lost-response example retries the same request and confirms one stored comment, not two.
After confirmation the composer clears. The comment still awaits moderation; replay does not bypass it.
Step 8
Closing an unsent comment asks first
- Use the detail Close control
- Read Leave this comment?
If you close the detail screen with unsent text, Leave this comment asks whether to discard it.
Read the warning before choosing. Closing the screen is not the same action as Send.
Step 9
Stay preserves the unsent text
- Choose Stay to continue editing
- Nothing is submitted
Choose Stay to return to the same detail screen with your unsent text intact.
Our genuine Stay action keeps the draft without making a comment request or posting anything.
Step 10
Leave discards without sending
- Choose Leave only if you want to discard
- The unsent comment is not posted
Choose Leave only if you want to discard the unsent comment and return to the board.
Our genuine Leave action submits nothing. If delivery was already uncertain, stay and retry safely rather than assuming the server has no copy.
Step 11
Guest identity and Pro have separate roles
- Use the private installation identity
- Pro is cosmetic, not permission
Pennie comments use the same private installation identity as your ideas and votes, regardless of main-app sign-in.
A Pro badge is cosmetic. It does not give a comment extra permissions, public visibility, or exemption from moderation.
Step 12
Read, write safely, then choose deliberately
- Send when ready, or Stay while editing
- Retry the same comment after uncertainty
Read the discussion, write safe constructive details, then deliberately send or discard your unsent text.
For uncertainty, retry the preserved comment. For pending moderation, wait rather than creating duplicate copies.