Make a request private

A request can stay private even when it belongs to a public board. Use this for account-specific feedback or details that should stay between the author and your team.

Change the request's visibility

Only workspace admins and owners can change this setting. The request keeps its current workflow status, so your team can continue reviewing, planning, or working on it.

Who can see a private request

Workspace admins and owners can see the request. Its author can also return to it when UserJot can identify them through their account or guest session. Other users cannot open it or find it on the public board or roadmap.

Sharing a link does not give someone access to a private request. Comments follow the request's access rules, and approving a comment does not make the discussion public.

Make it public again

Choose Public from the same dropdown. For the request to appear publicly, it must also belong to a public board and have completed any required moderation review.

A private board continues to restrict access even if an individual request is set to Public. See private boards if you want the same visibility rules for every request on a board.

Keep a request private during moderation

If a request is waiting for manual review or contains sensitive information, the review panel offers Keep private. This finishes the review and sets the request to Private in one step.

Changing the Public / Private dropdown by itself does not resolve a review. For possible spam or abuse, Keep clears those findings and preserves the visibility you have chosen. Other review reasons may still need attention.

Read moderate content for the full review flow.

Content that was already shared

Making a request private cannot take back copies people have already seen, downloaded, or received by email. Previously shared direct attachment links may still work. Remove sensitive details before publishing whenever possible.