Claron
    Documentation
    AUTHENTICATED PREVIEWSReviewed

    Authenticated Previews

    A page behind sign-in needs a valid review session before its protected content can be captured or checked. Configure a dedicated test account and verify access to the specific route you want reviewed.

    Before you start

    A dedicated test account and the protected route you want reviewed.

    What you get

    A preview that can reach the expected signed-in content before capture.

    Check access to a protected route

    INTERACTIVE EXAMPLE

    Preview the login check using a dedicated sample review account.

    StorefrontCheck access to a protected route
    Sandbox

    Authenticated preview

    Use test accounts and your application's supported sign-in flow.

    Configure hosted-preview authentication

    1. Open Project Settings → Build and the app's authentication/login configuration with project configuration permission.

    2. Configure the login URL and the supported form/account settings for a dedicated test account

      Use an account with only the access the review needs.

    3. Use the login test and read its result

      A successful homepage load is not a successful authenticated login.

    4. Open the intended protected route in the preview and confirm the expected signed-in content before starting the review.

    5. If automated capture cannot reproduce the sign-in state, check its login result, credentials, redirects, selectors, and supported authentication method before requesting a retake.

    Live-site extension reviews

    For the browser extension, sign in to the website normally in the authorized browser tab. The extension captures with the access available to that browser; it cannot bypass the site's authentication or network access rules.

    Live production annotations do not support automated retakes, after screenshots, or pixel comparisons. Verify a fix manually on the correct deployment.

    Login failures and sensitive data

    MFA, CAPTCHA, external identity-provider restrictions, and session expiry can prevent automated reproduction. Do not disable production access controls to force capture. Use a supported test flow or perform a permitted manual review.

    Avoid personal data in the review account. Captured page, console, and network evidence can contain application data, even when a password input is protected. Inspect the report's evidence before inviting reviewers.