Environments & Releases
An environment names the website target you review, such as staging or production. The selected build or deployment identifies the version, so a report and its verification can refer to the same intended target.
Before you start
Project configuration permission and the URL and branch for the target.
What you get
Reviews and verification tied to the right environment and version.
Configure a review environment
INTERACTIVE EXAMPLEChange the sample target and see the version context used for review.
Environment settings
A target URL and branch are distinct from a build or deployment ID.
Add or update an environment
Open the project's environment settings with project configuration permission.
Enter a recognizable name and unique key, then select its branch and URL as appropriate
Add environment to save a new target.
For an existing target, edit its settings and choose Save changes
Use Build to create a preview for an active environment.
Check the current build/deployment after a successful build or registered deployment
Disable an environment when it must no longer be selected for new work.
Check the review target
| Check | Why it matters |
|---|---|
| Environment and URL | Confirm the intended staging or production target. A URL alone does not identify the deployed version. |
| Build or deployment | Select the actual version being reviewed or verified. Check its branch, commit, and release where supplied. |
| Annotation filters | Compare reports from the same environment and version. A staging fix may not yet be deployed to production. |
| SDK configuration | Frontend configuration can supply CLARON_ENVIRONMENT, CLARON_RELEASE, and commit/deploy metadata. Updated backend setup lets you select the frontend environment by name or key; it resolves the ID automatically. |
Verify a version change
If source or backend evidence is missing, confirm the instrumentation is in this deployment and start a new review. A later release does not retrospectively capture an earlier request.
Deploy or build the fixed version and confirm the target environment points to it.
Request verification with that build or deployment selected.
Repeat the reported action on the target and record the decision
If a different environment was tested, correct the target rather than approving the wrong version.