# Browser permissions

Canonical: https://fairleadhq.com/docs/recorder/permissions/

Updated: 2026-10-08
Publication state: published
Product version: Source verified — 52de40a

Agent summary: Understand why Recorder requests access to browser data. Browser policy and protected pages can prevent capture despite broad host permission.

## Prerequisites

- Google Chrome on a computer

## Inputs

- Recorder permission requests and target-page requirements

## Outputs

- An understanding of capture access and restrictions

## Limitations

- Browser policy and protected pages can prevent capture despite broad host permission

## Permissions

- Website access and browser debugging for capture

## Privacy

- Review captured content before sharing


Understand why Recorder requests access to browser data.

Recorder needs website and browser debugging access to capture a test's actions, requests, and diagnostic messages. Use it only on pages you are permitted to test.

## What the permissions support

| Access | Purpose |
| --- | --- |
| Browser debugging | Capture network, console, exception, and related browser evidence |
| Website access and script injection | Record page interactions and support capture across eligible navigation |
| Tabs and navigation | Identify the recording tab and follow supported page transitions |
| Storage | Hold local session state and extension settings |
| Downloads | Write evidence files to your computer |
| Side panel | Keep recording and review controls alongside the page |
| Clipboard reading | Attach an image when you request a clipboard paste |
| Identity | Complete the Fairlead account connection flow |
| Alarms | Support background session activity |
| Offscreen document | Track browser color-scheme information for the toolbar icon |

## Website scope

Recorder requests broad all-site host access so it can operate on the test targets you choose. That browser permission does not override the recording's capture rules:

- **Without an account:** capture follows the starting page's **hostname family**.
- **Signed in with a project:** capture follows the restrictions your organization configures for the selected project, including page and network domain rules. Signing in does not bypass those rules.

See [capture configuration](https://fairleadhq.com/docs/recorder/capture-configuration/) for how these rules affect recorded evidence.

Capture begins after **Start recording**. Read [Navigation, tabs, and frames](https://fairleadhq.com/docs/recorder/navigation-and-frames/) for how scope affects the evidence.

## Restricted pages and files

Chrome internal pages and other protected browser surfaces cannot be captured. Local account-free recording also excludes `file:` pages. A connected capture of local files additionally depends on Chrome granting file access and on the project's rules.

A browser or organisation policy can prevent debugging or site access. If recording fails, review the reported error and ask the administrator responsible for that policy.

## Separate access from sharing

A browser permission enables capture; it does not decide which evidence you should send to a team. [Review the data](https://fairleadhq.com/docs/recorder/review-redaction/) and understand the [destination](https://fairleadhq.com/docs/recorder/privacy/) before downloading or submitting it.