Secure Public Links
Request Mark public boards are designed for controlled sharing. A board link includes a board ID, public key, and refId so teams can collect feedback from intended users while keeping the experience lightweight.
When it helps
Why teams use this
Scattered feedback slows small teams down
startups, indie hackers, SaaS teams, and micro-SaaS builders often hear requests across email, support, calls, chat, and founder replies. Request Mark gives that signal a structured place to live.
Internal tools are not public feedback tools
Delivery tools are useful after a decision is made. A feedback board helps users submit, vote, and follow requests before work becomes an internal ticket.
Visible progress builds trust
Statuses and admin updates help users understand whether a request is new, planned, in progress, shipped, or closed.
What this helps you do
After setup
What improves after setup
A clearer intake path
Teams get one page to share when a customer asks for a feature, instead of manually copying notes into a spreadsheet or backlog.
Better prioritization signals
Votes, comments, requester identity, and status history create a more useful demand picture than memory or gut feel.
A faster path to delivery
When a request has enough signal, the team can move it into Linear, Trello, or the delivery system that owns implementation.
How it works
- 1Create a board and keep its public key private to intended channels.
- 2Generate a link with a refId for each customer or account.
- 3Share the link where feedback is requested.
- 4Take the board offline when the collection window ends.
FAQ
What does the public key do?+
The public key acts as the access secret for a board. Request Mark only loads the public board when the board ID, key, and refId are present.
Can a board be taken offline?+
Yes. A founder can switch a board offline from the dashboard without deleting feedback.