What is a dock?

A dock is Layerdock's core unit of work: one site, one review workspace, one shareable link. When you create a dock for a website, Layerdock generates a single review link tied to that site. Anyone you send the link to can open it, install the Layerdock browser extension once, and immediately start pinning feedback directly onto the live page — they never create a Layerdock account, set a password, or get added to your team. Each pin they leave automatically captures the exact element, a screenshot, the page's console errors, and any failed or slow network requests from that moment, so the person who fixes it never has to ask “where exactly?” or reproduce the bug from scratch. A dock can hold multiple build layers, so feedback on your staging release and feedback on last week's release stay in separate threads instead of one scrambled list.

Why “dock” and not “project”?

Most feedback tools call this a “project,” which implies internal team management — tickets, assignees, sprints. A dock is deliberately narrower: it's the review surface for one site, built around the fact that most of the people leaving feedback on it (clients, stakeholders, QA testers) aren't on your team and shouldn't need an account to use it.

What happens inside a dock?

• Reviewers open the review link and pin comments directly onto the live site.
• Each pin captures the element, screenshot, console errors, and network requests automatically.
• Feedback can be filtered by build layer, status, viewport, or assignee.
• Your team resolves pins from the dashboard, with the full diagnostic context attached.

New to the category? Compare the website feedback tools side by side, read the setup guides, or go straight to pricing.