Choose your starting point
| Your goal | What to set up |
|---|---|
| Review a repository preview | Follow Quick Start to connect a repository, build a preview, and start a review. No CLI installation is required. |
| Report an issue on an existing website | Use the browser extension with an approved project and domain. Your website stays on its existing host. |
| Identify a React element's source file | Add the frontend SDK to your build, then make a new deployment. |
| Inspect the server request behind an issue | Enable backend evidence. A separate backend needs the optional backend SDK. |
| Read issue evidence in a coding assistant | Connect the read-only MCP server. |
| Review or apply a suggested fix locally | Install and authenticate the CLI in the correct repository checkout. |
The terms used in these guides
| Term | Meaning |
|---|---|
| Workspace | Your organization and its people, billing, and shared settings. |
| Project | One website or application, its reviews, builds, team, and issues. |
| Annotation / issue | A report attached to a page, element, console entry, or network request. |
| Build / deployment | The version of the website being reviewed. A deployment may be hosted by Claron or by you. |
| Environment | A named target such as staging or production, with its own review context. |
Choose the right role
Project owners manage the project. Developers investigate and fix issues; testers triage and verify them. Clients and guests can report and discuss public issues in their permitted review context. They cannot read internal staff comments or use MCP for that project.
Workspace roles and project roles are separate. Use Team & Roles before inviting a reviewer or granting diagnostic access.
Find work and manage your account
Use Dashboard for a project overview, My Work for assigned tasks and decisions, and Workspace Search to find an issue. Review Notifications and Billing to configure alerts and understand your current account limits.