# Preferences

> Account-wide feature toggles for healing, screenshots, review management, accessibility, AI features, the recorder profile, and asset delivery.

**Settings > Preferences** holds the account-wide feature toggles. A change here applies to every project, and several of these gate features documented elsewhere, so a feature that appears missing is often a toggle that is off.

Some toggles are hidden until Testsigma support enables them for your account.

## Execution and healing

| Preference | What it does |
|---|---|
| **Auto Healing** | Corrects an element automatically during a run when it fails, by identifying what changed in the new build. See [Elements](https://testsigma.com/docs/v2/create-and-manage/elements/) |
| **Generative AI Autoheal** | Uses generative AI to heal broken element locators during execution |
| **Test case level multi driver session** | Allows naming and running several driver sessions within a single test case. The launch app step then exposes a session name field for local executions |

## Who can stop an execution

**Control Who can Stop Executions** is off by default, which means anyone can stop any execution. Turning it on splits that by role:

- **Account Administrators** and **Super Administrators** can stop any execution, from **Usage Details** or **Run Results**
- **Test Managers**, **Test Leads**, and **Automation Engineers** can view every execution but can stop only the executions and inspector sessions they started themselves

## Screenshots and reports

| Preference | What it does |
|---|---|
| **Highlight element in screenshot** | Marks the object a step interacted with, so a screenshot shows what the step touched. Applies only to web steps that contain an element |
| **Screenshot with timestamp** | Overlays each execution screenshot with its capture time |
| **Detailed accessibility report** | Puts a highlighted screenshot in the accessibility PDF for every occurrence of an issue. Off means a brief report with one sample screenshot per issue |
| **Design Visual Validations** | Compares execution screenshots against Figma design assets. Needs the Figma integration configured |

## Review management

A parent toggle with 3 children, all off by default:

- **Test Case Review Management**: lets Test Managers review test cases and share feedback in one place
- **Element Review Management**: lets Test Managers review elements
- **Self-Review Management**: lets test developers review their own test cases and elements

See [Review management](https://testsigma.com/docs/v2/settings/review-management/).

## Web accessibility testing

- **Web Accessibility Testing - Step level**: runs accessibility checks on the steps you enable them for
- **Web Accessibility Testing - Plan level**: **deprecated**. It ran checks for a whole test plan

Plan-level accessibility testing is deprecated. Use step level instead.

See [Accessibility testing](https://testsigma.com/docs/v2/testing-types/accessibility-testing/).

## Generative AI

A parent toggle with 3 children:

- **Generative AI features in Recorder**: Copilot's step generation inside the recorder
- **Generate test cases from Swagger schema**: API test case generation from a `.json`, `.wsdl`, or `.xml` schema
- **Generate Test Data Profile**: the Test Data Generator agent

## Agentic AI

A parent toggle covering the agents, described as generating, maintaining, planning, and analyzing your tests.

- **Autonomous Testing**: agents analyze run results, identify the issues, and create bug reports
- **Generator (Live App)**: the Generator agent learns your live application and creates executable test cases from business requirements

**Analyzer & Bug Reporter** is a separate toggle rather than a child of **Agentic AI**, and it gates the Analyzer and Bug Reporter agents.

See [AI agents](https://testsigma.com/docs/v2/atto/ai-agents/) and [Agentic execution](https://testsigma.com/docs/v2/atto/agentic-execution/).

## Copilot and recorder extension

This one is a radio group rather than a toggle, and it decides how the recorder extension reaches the browser Testsigma launches for a Copilot session.

| Mode | How the extension is loaded |
|---|---|
| **Automatic** | Testsigma loads its bundled recorder extension into the browser on every session. The default |
| **Managed profile** | The Chrome Web Store extension is installed once into a Testsigma-managed browser profile and reused across sessions |
| **Your own browser profile** | Sessions run in a browser profile your team manages, and the recorder extension has to be installed in that profile |

See [Copilot](https://testsigma.com/docs/v2/atto/copilot/#set-up-a-browser-profile-for-recording).

## Asset delivery

| Preference | What it does |
|---|---|
| **Use asset proxy** | Routes test assets through the Testsigma asset proxy instead of accessing them directly from storage |
| **Use CDN signed URLs** | Serves test assets through time-limited signed CDN URLs |