✓ Small teams with repeated customer-story requests
✓ Readers comparing concrete collection and review requirements
✓ Businesses needing an understandable publication inventory
— Fake reviews or manufactured endorsements
— Regulated advice or legal-compliance certification
— Generic CRM, course delivery or agency project management
Absence from a page is not access control
A response can be missing from a website collection yet remain available somewhere else. List the actual surfaces: account view, hosted sharing page, widget, downloaded file and social post. A visibility change in one surface does not necessarily change every other copy. Review the behavior of each route instead of relying on the everyday meaning of a status word.
Use the documented distinction
Boast describes Private and Needs Review as internal-only, Unlisted as shareable but not displayed in widgets, and Published as shareable and widget-eligible. Its social-sharing documentation also describes a thank-you-page path that makes submitted content accessible by direct link. Check current settings before enabling that route for material that must first pass review.
Write an explicit hold case
A fictional customer submits a useful clip but asks a question about attribution. Your intended outcome might be that no public link or widget exposes it until clarification. Document that outcome and inspect all relevant sharing controls. This is a proposed acceptance case, not a claim that we have tested a particular account or verified every integration.
Explain the state to the team
Avoid vague instructions such as hide this for now when several mechanisms can hide different things. Specify remove from widget, stop direct sharing or retain only in the internal review queue as appropriate. A clear request reduces the chance of a colleague sending a link to a supposedly private item. For already distributed files, treat retrieval or removal as a separate task rather than assuming a status change recalls them.
An original decision example
Illustrative visibility matrix: internal reviewer can inspect the held item; an ordinary visitor must not see it in a widget or open it by a distributed link. Test those surfaces separately through supported controls. Do not assume an item is private merely because a homepage search or visual inspection did not reveal it.
Where the safety evidence stops
This guide draws on Boast response visibility states, Boast response social sharing and direct links. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Boast response visibility states — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast response social sharing and direct links — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24