When should two feedback notes point to the same feature?
Link both notes if they support the same change. One person might need a receipt for bookkeeping and another for reimbursement. Keep the two reasons as evidence under the proposed download feature. That gives you more context than one combined vote count.
Who can see a Productboard portal shared by private link?
Anyone with the link can open its visitor view. Productboard documents a separate Company option for workspace contributors and viewers and a Hidden option for makers and admins. Keep sensitive evidence in the appropriate internal space. Portal card updates can reach people who voted or, with the applicable update option, people whose feedback is linked. Review the recipient choice first.
Who counts toward the bill, and who can export?
Productboard’s pricing is based on makers, the people who edit and manage product work. Check that role separately from the people who only contribute feedback. Makers and admins can export features to CSV. That file covers the feature data they can access. Check the separate feedback export if you also need the underlying notes.
Can you explain the decision using two different notes?
Write two fictional notes on paper. Link them to Download receipts only if the proposed change meets both needs.
- Keep each reasonRecord bookkeeping on one note and expense reimbursement on the other.
- Write the public cardDescribe the download task without either person’s account details. Compare what belongs on the card with what belongs in the internal notes.