More ways to bring feedback together
Choose the workflow your project needs, then set its access and review the evidence.
- Choose a workflow
- Set access
- Review evidence
| You need | Use | Keep in mind |
|---|---|---|
| A client’s reply | Guest discussion link | One discussion; guests see the original text, not screenshots or existing replies |
| New guest requests | Guest feedback link | Submission only; no access to your workspace |
| PDF or image comments | Document review | Project access applies; documents are not exposed to guest links |
| Text feedback on your site | Website widget | Exact approved origins; no screenshot or recording capture |
| Ratings and written responses | Surveys and NPS | Opt-in responses stay separate from threads |
| Recurring public-page checks | Scheduled QA | Inspect run history and visual baselines; authenticated flows are outside these checks |
| Screen feedback in your app | Native mobile SDK | iOS/Android host integrations; no standalone Store app |
| Thread activity notifications | Signed webhooks | Your HTTPS receiver gets event identifiers and revisions, not thread text or screenshots |
Guest links, widgets and surveys need configured Turnstile. Choose expiry and response/submission limits deliberately; revoke guest access when finished. Enable Documents and Surveys under Project settings → Project → Optional tools when needed.
Organize the work
Use assignments, work-status filters, categories, tags, saved views and individual point progress. Link delivery evidence and verify the result before resolving. Work through a review queue.
For custom integrations, API, MCP and CLI provide authorized reads and writes through the same server operations.