Bring community feedback into Discovery

You need current authority for the source content and access to the relevant Evidence workflow. Open the post or conversation in portal administration.

A published post, reply or poll is not automatically an Insight or a roadmap decision. Use capture when specific feedback should become part of your product evidence, then review it in Discovery.

1. Open the content’s management controls and choose More post actions → Save as evidence in Zentrik.
2. Select the post or replies that belong in the capture. Do not include unrelated conversation simply because it is available.
3. Preview the selected source count and inspect its text and attribution. The preview identifies the imported source as a Signal; it is source material, not an automatically approved Insight.
4. Explicitly approve the selected content and start the capture.
5. Inspect its status and open the resulting Evidence in Zentrik when available.

Read what is being copied before approval. Customer names, private context and mixed-group conversations require the same care here as when publishing. The capture is a deliberate product record; it is not a live mirror that silently rewrites itself whenever someone edits the conversation.

A later post/reply edit can mark captured content for review. Open the source comparison to understand what changed, then record the appropriate review decision through the available controls.

An immutable captured snapshot preserves what was approved. It does not confer ongoing permission to read the original conversation. Source removal, moderation or reduced grants can make the current source unavailable without making it appropriate to reconstruct or disclose it elsewhere.

If an import is held or fails, inspect the reason and review current permissions and source state before retrying. A queued capture is not evidence that the final record already exists.

Open the created record and check the selected content, attribution and source reference. Confirm that excluded replies were not included and that the record belongs to the intended workspace.

Use Evidence to insights to review what the source supports, then Insights to opportunities when identifying a recurring customer need. Combine the captured feedback with other evidence rather than treating one contribution as a complete product case.

Publishing a learning update back to the community is a separate customer-facing action. Internal Evidence does not become public because it came from a portal conversation.