---
title: "Core concepts"
description: "SmartestQA in one page: company, projects, environments, actions, requirements, test cases, data, pipelines, run modes, agents, reports, auto-heal, tasks, AI and MCP."
url: https://docs.smartestqa.ai/en/concepts.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "concepts mental model overview company project project type web mobile desktop environment dev test prp start page url page action locator app map module note requirement sub-requirement test case step template variable data source dataset api request pipeline phase setup before after teardown dry run pipeline run schedule agent runner smartest server device farm report live log insight auto-heal task ai mcp roles"
---
# Core concepts

SmartestQA has a small set of building blocks that every screen reuses. Learn them once and every module reads the same way: what you capture, what you build from it, where it runs and what it leaves behind.

## In short

**On this page you can**

- Learn the building blocks: company, project, action, test case, pipeline, report.
- See how DEV, TEST and PRP and the start page URL decide what a test opens.
- Tell a dry run from a pipeline run , and a test agent from the Smartest Server.
- Find where each AI feature lives, from Enable AI to MCP assistants.
- Jump from each concept to the page that explains it in detail.

**How to use it**

1. Create a project of the right type and add a start page URL with a TEST address.
2. Capture pages and actions in Discover , then write requirements in Analyze .
3. Build test cases from those actions in Automate and try them with Dry Run .
4. Put the test cases in a pipeline in Schedule and run it on the server or an agent.
5. Read the report, review repairs in Maintain and work the tasks that failed runs created.

**At a glance**

- **The account:** A **company** holds users, the licence and **projects**. One project tests one application: WEB, MOBILE or DESKTOP.
- **Order of work:** The main menu, top to bottom: Discover, Analyze, Automate, Schedule, Report, Maintain.
- **What you build:** **Actions** (controls with locators), **requirements**, **test cases** made of steps, and **pipelines** that run them.
- **Where tests run:** The **Smartest Server**, a **test agent** on your machine, or a device farm for phones.
- **What stays:** Every pipeline run writes a **report**. A dry run shows a live log only.
- **AI:** Optional per project. It names controls, writes requirements and steps, explains failures and repairs locators. Assistants such as Claude connect through **MCP**.

## Start from your question

I want to…

- [See how the pieces connect](https://docs.smartestqa.ai/en/concepts.html#how-it-connects)
- [Pick the right project type](https://docs.smartestqa.ai/en/concepts.html#project-types)
- [Know which kind of run to use](https://docs.smartestqa.ai/en/concepts.html#run-modes)
- [Decide where my tests run](https://docs.smartestqa.ai/en/concepts.html#where-tests-run)
- [Look up a word I saw on screen](https://docs.smartestqa.ai/en/glossary.html)

Something is wrong

- [Find my problem by symptom](https://docs.smartestqa.ai/en/troubleshooting.html)
- [My test ran but Report is empty](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-empty-report)
- [A step typed {{name}} literally](https://docs.smartestqa.ai/en/automate-troubleshooting.html#fix-literal-variable)
- [My agent shows offline](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-agent-offline)
- [I deleted items but still hit the limit](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-limit-reached)

How does it work?

- [Test agents versus autonomous agents](https://docs.smartestqa.ai/en/concepts.html#two-agents)
- [What DEV, TEST and PRP change](https://docs.smartestqa.ai/en/concepts.html#environments)
- [Where a {{variable}} gets its value](https://docs.smartestqa.ai/en/concepts.html#test-data)
- [What auto-heal changes, and who approves it](https://docs.smartestqa.ai/en/concepts.html#auto-heal)
- [Which AI features exist and where to switch them](https://docs.smartestqa.ai/en/concepts.html#ai-features)

## How the pieces connect

Read this list top to bottom once. Each line builds on the one before it, and each concept links to its own section below.

1. A [company](https://docs.smartestqa.ai/en/concepts.html#company-project) has users with a [role](https://docs.smartestqa.ai/en/concepts.html#roles), a licence and one or more [projects](https://docs.smartestqa.ai/en/concepts.html#company-project).
2. A project tests one application. Its [start page URLs](https://docs.smartestqa.ai/en/concepts.html#environments) hold one address per environment: DEV, TEST and PRP.
3. [Discover](https://docs.smartestqa.ai/en/concepts.html#app-knowledge) captures the app: **pages**, the **actions** on each page with their **locators**, the **App Map** and your **Notes**.
4. [Analyze](https://docs.smartestqa.ai/en/concepts.html#requirements) holds what the app must do: main requirements split into testable sub-requirements.
5. [Automate](https://docs.smartestqa.ai/en/concepts.html#tests) builds **test cases**. Their steps point at actions, so fixing one locator fixes every test that uses it. Test cases link to sub-requirements.
6. [Test data](https://docs.smartestqa.ai/en/concepts.html#test-data) feeds the steps: variables, Data Source keys, datasets, database and Kafka connections. [API requests](https://docs.smartestqa.ai/en/concepts.html#api-requests) become API steps.
7. A [pipeline](https://docs.smartestqa.ai/en/concepts.html#pipelines) in Schedule runs a list of test cases (or requirements) in one environment, by hand, on a schedule, from CI or from a trigger.
8. The run executes [somewhere](https://docs.smartestqa.ai/en/concepts.html#where-tests-run): on the Smartest Server, on a test agent or on a device farm.
9. Every pipeline run writes a [report](https://docs.smartestqa.ai/en/concepts.html#results). InSight adds the numbers up across runs. A [dry run](https://docs.smartestqa.ai/en/concepts.html#run-modes) writes no report.
10. When a locator breaks, [auto-heal](https://docs.smartestqa.ai/en/concepts.html#auto-heal) repairs it and a person reviews the repair in Maintain. Failed runs can create [tasks](https://docs.smartestqa.ai/en/concepts.html#tasks).
11. [AI](https://docs.smartestqa.ai/en/concepts.html#ai-features) helps at every step when it is on, and [MCP](https://docs.smartestqa.ai/en/concepts.html#ai-features) lets an assistant such as Claude do the same work with your approval.

### Where each thing lives in the menu

| Menu item | What you keep there | Explained in |
| --- | --- | --- |
| InSight | The home dashboard: run results and test health across the project. | [InSight](https://docs.smartestqa.ai/en/insight.html) |
| Discover | Actions, App Map pages, modules and Notes. | [Discover](https://docs.smartestqa.ai/en/discover.html) |
| Analyze | Requirements, their folders and project documents. | [Analyze](https://docs.smartestqa.ai/en/analyze.html) |
| Automate | Test cases, templates and their folders. | [Automate](https://docs.smartestqa.ai/en/automate.html), [Step reference](https://docs.smartestqa.ai/en/automate-steps.html) |
| Schedule | Pipelines, scheduled runs, triggers and queues. | [Schedule](https://docs.smartestqa.ai/en/schedule.html) |
| Report | One report per pipeline run. | [Report](https://docs.smartestqa.ai/en/report.html) |
| Maintain | Auto-heal reviews, AI steps and network captures to convert. | [Maintenance](https://docs.smartestqa.ai/en/maintenance.html) |
| Agents | Autonomous AI agents of the project. | [Autonomous Agents](https://docs.smartestqa.ai/en/ai-agents.html) |
| Data Source | Keys, datasets and database and Kafka connections. | [Data Source](https://docs.smartestqa.ai/en/data-source.html) |
| API Requests | Saved HTTP requests in collections and folders. | [API Requests](https://docs.smartestqa.ai/en/api-requests.html) |
| Device Farm | Test agents, and for mobile: nodes, devices and the App Library. | [Agent Pool & Device Farm](https://docs.smartestqa.ai/en/agent-pool.html) |
| Deploys & Repos | Code repositories and the deploys your CI reports. | [Deploys & Repos](https://docs.smartestqa.ai/en/deployments.html) |
| Tasks | Defects and work items, many created by failed runs. | [Tasks](https://docs.smartestqa.ai/en/tasks.html) |
| Configuration | Project Panel, Company Settings, Integrations and Logs (Admins). | [Project settings](https://docs.smartestqa.ai/en/project-settings.html), [Company settings](https://docs.smartestqa.ai/en/company-settings.html), [Integrations](https://docs.smartestqa.ai/en/integrations.html), [Logs](https://docs.smartestqa.ai/en/logs.html) |

## Company and project

- **Company:** Your account. Users, projects, the licence and billing belong to it. Whoever signs up becomes its first Admin. See [Create your account](https://docs.smartestqa.ai/en/quick-start-account.html).
- **Project:** One application under test. Actions, requirements, test cases, pipelines, reports, data and integrations all belong to one project. See [Create a project](https://docs.smartestqa.ai/en/quick-start-project.html).
- **Sample project:** A finished example project created once per company, with actions, tests, a pipeline and reports. It does not count against the licence. See [Sample project](https://docs.smartestqa.ai/en/quick-start-project.html#sample-project).
- **Licence limits:** Your company’s licence can limit users, projects, test cases, requirements, pipelines, pipeline runs and parallel threads. Counters count what you create, so deleting does not give capacity back. At a limit you see “Company license limit has been reached…”. An Admin sees the licence in [Company Settings › Billing](https://docs.smartestqa.ai/en/company-settings-billing.html).

### Project types: WEB, MOBILE, DESKTOP

The type decides how you capture the app and where its tests can run. API, database, mail and load-test steps work in every type, so you do not need an extra project for them.

| Type | For | Capture with | Tests run on |
| --- | --- | --- | --- |
| WEB | Anything that opens in a browser. | The Chrome or Edge extension: [**Discover Your App**](https://docs.smartestqa.ai/en/discover-your-app.html#step-by-step) and **Record Actions**. | The Smartest Server or your test agent. |
| MOBILE | Native or hybrid Android and iOS apps; one project covers both. | The Appium inspector on a device or emulator. | Your agent with a local device, SmartTest Device Farm, AWS Device Farm or BrowserStack. |
| DESKTOP | A desktop application. The platform is set in Desktop Configuration (Windows by default, or macOS). | The Desktop Recorder through the agent. | Only your agent, on the machine where the app is installed. |

More: [Which project type?](https://docs.smartestqa.ai/en/quick-start-project.html#project-type), [Mobile & desktop capture](https://docs.smartestqa.ai/en/discover-mobile-desktop.html), [Mobile Config](https://docs.smartestqa.ai/en/project-settings-mobile.html), [Desktop Configuration](https://docs.smartestqa.ai/en/project-settings-desktop.html).

## Environments and start page URLs

- **Environment:** Which installation of your app a recording or run uses: **DEV**, **TEST** or **PRP**, PRP being the production-side environment. Test cases follow the pipeline’s environment, so one set of tests serves all three. See [Start page and environment](https://docs.smartestqa.ai/en/schedule-where.html#environment).
- **Start page URL:** A named address with one value per environment, where web recordings and runs begin. One of them is the project’s default. An environment with no address is greyed out (“No URL defined for this environment”). See [Add a start page URL](https://docs.smartestqa.ai/en/quick-start-connect.html#start-page-url) and [Start pages](https://docs.smartestqa.ai/en/project-settings-project.html#start-pages).
- **Environment-specific key:** A Data Source key whose name ends in `_DEV`, `_TEST` or `_PRP`. A run in that environment uses it instead of the key without the suffix, for example a different API address per environment. See [Environment variants](https://docs.smartestqa.ai/en/data-source-variables.html#environments).
- **Deploy environment:** Deploys & Repos also accepts names you add, such as STAGING. Pipelines still run on DEV, TEST or PRP only. See [Deploys & Repos](https://docs.smartestqa.ai/en/deployments.html#concepts).

> **Warning: PRP is real**
>
> Tests on PRP create orders, send e-mails and change data in production. Record and build on TEST with a test user, and run only agreed read-only checks on PRP.

## What SmartestQA knows about your app (Discover)

- **Page:** A name that groups actions, such as `checkout`. Pages are created by naming them; there is no separate create step. See [Page names](https://docs.smartestqa.ai/en/discover-your-app.html#page-names).
- **Action:** One control on one page, for example `Click Sign In` on page `login`, with a type, its locators, an optional **Navigates To** page and a screenshot. Steps point at actions by ID, so a fixed locator fixes every test that uses it. See [Actions](https://docs.smartestqa.ai/en/discover-actions.html).
- **Locator:** How a test finds the control: `id`, `name`, `css`, `xpath`, `accessibility_id`, `resource-id`, `class`, `linktext` or `tagname`. Recorded actions keep fallback locators. See [Locator chip](https://docs.smartestqa.ai/en/discover-numbers.html#locator-chip).
- **App Map:** Every page as a record: purpose, preconditions, expected outcomes, risk, roles, screenshots and where it leads. **Update map** builds it from your actions. The AI reads it when it writes requirements and tests. See [App Map](https://docs.smartestqa.ai/en/discover-app-map.html).
- **Module:** A business area such as **Orders**. A module groups pages in the App Map, and the same module is the top-level folder in Analyze and Automate. See [Modules](https://docs.smartestqa.ai/en/discover-app-map.html#modules).
- **Note:** One rule or fact about the app that no scan can see, such as “Orders over €10,000 need a second approver”. Active notes are sent to the AI. See [Notes](https://docs.smartestqa.ai/en/discover-notes.html).

## Requirements (Analyze)

- **Main requirement:** A feature or user flow, for example **Pay with a saved card**. It is a row in the requirement tree. See [Write requirements](https://docs.smartestqa.ai/en/analyze-requirements.html).
- **Sub-requirement:** One testable condition with an expected result inside a main requirement. Test cases are linked here, and coverage is counted over sub-requirements. See [Link test cases](https://docs.smartestqa.ai/en/analyze-test-cases.html).
- **Assessment:** An AI review of a main requirement and its subs, with a Quality Score from 0 to 100. The score rates the text, not whether it is tested. See [AI assessment](https://docs.smartestqa.ai/en/analyze-assessment.html).
- **Requirements from documents:** The [**Analyze with AI**](https://docs.smartestqa.ai/en/analyze-import.html#step-import) wizard turns a spec or screenshot into requirements and test cases. See [Generate from documents with AI](https://docs.smartestqa.ai/en/analyze-import.html).

## Test cases and steps (Automate)

- **Test case:** An ordered list of steps that runs on its own and produces a report when a pipeline runs it. See [Test cases and folders](https://docs.smartestqa.ai/en/automate-test-cases.html).
- **Step:** One thing the test does. An **action step** uses a shared action (click, type, select). A **step-type step** has its own dialog: Assertion, Python, JavaScript, AI, API, Network, Database, Mail, Kafka, Global parameter, JMeter or k6. See [Step reference](https://docs.smartestqa.ai/en/automate-steps.html).
- **Template:** A test case used as one step inside other test cases, such as a login. Editing it changes every test that uses it. See [Templates](https://docs.smartestqa.ai/en/automate-steps-flow.html#template).
- **Recording:** The fastest way to start a test: the extension (web), the inspector (mobile) or the Desktop Recorder writes the steps and the actions they use. See [Record and add steps](https://docs.smartestqa.ai/en/automate-add-steps.html).
- **Archive:** Where removed test cases and folders go. Restoring brings them back, but not into the pipelines they were removed from. See [Archive](https://docs.smartestqa.ai/en/automate-test-cases.html#archive).

## Test data: variables, Data Source and datasets

Steps never need a hard-coded value. They read it by name when the step runs:

| Written as | Comes from | Explained in |
| --- | --- | --- |
| `{{name}}` or `{{tc:name}}` | A value an earlier step saved in this run (a Get step, an API extraction, a mail OTP, a code step). | [Data and variables](https://docs.smartestqa.ai/en/automate-steps-variables.html#syntax) |
| `{{ds:key}}` | A Data Source key: a typed value, a dataset cell or a database query. Encrypted keys hold passwords and tokens. | [Variables (keys)](https://docs.smartestqa.ai/en/data-source-variables.html), [Secrets](https://docs.smartestqa.ai/en/data-source-secrets.html) |
| `{{excel:name}}_column` | A column of a dataset uploaded from Excel or CSV. A pipeline can run the test once per row; a dry run uses the first row. | [Datasets](https://docs.smartestqa.ai/en/data-source-datasets.html), [Run once per row](https://docs.smartestqa.ai/en/automate-test-data.html#data-driven) |

- **Data Source:** The project’s store of keys, datasets and connections. Tests reference them by name, so nothing secret sits in a step. See [Data Source](https://docs.smartestqa.ai/en/data-source.html).
- **Connection:** A database (JDBC) or Kafka login that Database and Kafka steps use. The password lives in the connection, never in a test. See [Connections](https://docs.smartestqa.ai/en/data-source-connections.html).
- **Global parameter:** A value a step stores under a project-wide name. Later runs can read it, which is why a skipped step can leave a value from an earlier run. See [Where a variable gets its value](https://docs.smartestqa.ai/en/automate-test-data.html#resolution).
- **Pipeline parameter:** A value a step types or selects, changed for one pipeline only. The test case in Automate keeps its own value. See [Pipeline Parameters](https://docs.smartestqa.ai/en/schedule-settings.html#pipeline-parameters).

A name that no source provides is typed as written, for example `{{orderNo}}`. See [The test typed {{name}} literally](https://docs.smartestqa.ai/en/automate-troubleshooting.html#fix-literal-variable).

## API requests

The API Requests library holds saved HTTP calls in collections and folders. You import them from Postman, Swagger / OpenAPI or curl, try them with **Send** from the SmartestQA server, and add them to test cases as API steps. Each API step keeps its own copy of the request, so later edits in the library do not change existing tests. See [API Requests](https://docs.smartestqa.ai/en/api-requests.html) and [The step’s own copy](https://docs.smartestqa.ai/en/api-requests-in-tests.html#copy).

## Pipelines (Schedule)

- **Pipeline:** A named, saved run plan: a run list plus the settings to run it. Some messages call it a scheduler. See [Schedule](https://docs.smartestqa.ai/en/schedule.html).
- **Run list:** What the pipeline runs, in order: test cases, or requirements (their linked test cases), plus other pipelines as **sub-pipelines**. Test cases and requirements cannot be mixed. See [Add content](https://docs.smartestqa.ai/en/schedule-create.html#add-content).
- **Phases:** **Setup** runs once at the start, **Before** before each test, **Test** is the check itself, **After** after each test, **Teardown** once at the end. If Setup fails the tests are skipped; Teardown always runs. See [Setup, Before, After and Teardown](https://docs.smartestqa.ai/en/schedule-create.html#phases).
- **Period:** When the pipeline starts by itself: Real-time (never by itself), Daily, Weekly, Monthly or Custom (Cron). See [Schedule a pipeline](https://docs.smartestqa.ai/en/schedule-timing.html).
- **Run Environment:** Where the run executes: a SmartestQA server, your agents, or a mobile device farm. See [Run Environment](https://docs.smartestqa.ai/en/schedule-where.html#run-environment).
- **Trigger and queue:** A trigger starts a pipeline when a webhook is called, an e-mail arrives or a file lands in a folder. A queue runs one pipeline run per work item. See [Triggers & queues](https://docs.smartestqa.ai/en/schedule-triggers-queues.html).

A pipeline copies the project’s run settings when it is created and keeps its own copy after that. See [How settings reach a run](https://docs.smartestqa.ai/en/project-settings-test-management.html#how-settings-reach-runs).

## Run modes: dry run, pipeline run, agent

A test case runs in one of two modes. An agent is not a third mode: it is a place where either mode can run.

|  | Dry run | Pipeline run |
| --- | --- | --- |
| Started from | [**Dry Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#start-dry-run) in the Automate editor | A pipeline: **Run** or [**Save & Execute**](https://docs.smartestqa.ai/en/quick-start-first-test.html#step-6), a schedule, CI/CD, a trigger or a queue |
| Use it to | Try a test while you build it | Keep results, run nightly, gate a release |
| Report | No. Live log only; screenshots are deleted after one hour | Yes, with screenshots, logs and video |
| Dataset rows | First row only | One run per row when the pipeline asks for it |
| Retries, stop, status icon | None; cannot be stopped; icon unchanged | The pipeline’s own Retry Count; can be stopped; icon updated |

Full comparison: [Run modes](https://docs.smartestqa.ai/en/automate-dry-run.html#run-modes). A **scheduled run** is simply a pipeline run started by its Period. See [Run, stop and follow](https://docs.smartestqa.ai/en/schedule-runs.html).

## Where tests run: server, agent, runner, device farm

- **Smartest Server:** SmartestQA’s own test servers. [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) runs the browser there, headless, with nothing to install. It reaches apps open to the internet, not your internal network. Runs wait in a fair queue when all slots are busy. See [Run on Server](https://docs.smartestqa.ai/en/schedule-where.html#server).
- **Test agent:** The SmartestQA client on a computer you control (also called a host). It runs tests there and sends logs, screenshots and video back. Every user has a personal **Localhost** agent; shared agents serve the whole company. See [Test Agents](https://docs.smartestqa.ai/en/agent-pool-agents.html).
- **Runner:** The part of SmartestQA that executes a test case step by step, finds elements, retries and heals. It works on the Smartest Server and inside your agent. Run logs quote it as “the runner”.
- **Device Farm:** Phones, tablets and emulators connected through **nodes**, with an **App Library** of builds to install. You can run tests on a device or take it for a live session. Mobile projects can also use AWS Device Farm or BrowserStack. See [Agent Pool & Device Farm](https://docs.smartestqa.ai/en/agent-pool.html).

| Your situation | Run on |
| --- | --- |
| Web app reachable from the internet | The Smartest Server |
| Web app behind a VPN or firewall, or steps that reach an internal database, mailbox or API | An agent inside that network |
| Phone or emulator on your desk | Your agent, with Appium |
| Real devices you do not own | SmartTest Device Farm, AWS Device Farm or BrowserStack |
| Desktop application | Your agent on the machine with the app |

Do you need an agent at all? See [Quick Start](https://docs.smartestqa.ai/en/quick-start-connect.html#agent).

> **Note: Two kinds of “agent”**
>
> A **test agent** (Device Farm › [**Test Agents**](https://docs.smartestqa.ai/en/agent-pool-agents.html#agent-list)) is a program that runs your tests on a machine. An **autonomous agent** (menu **Agents**) is an AI job that reviews runs, writes reports and proposes changes. They are unrelated; this documentation always says which one it means.

## Results: report, live log and InSight

- **Report:** The stored record of one pipeline run: its verdict, every test case attempt, each step’s status, log, screenshot and durations, and video. You can export it as PDF or share it by e-mail. See [Report](https://docs.smartestqa.ai/en/report.html).
- **Live log:** The Test Run panel that streams while a run is going. It is not kept. Dry runs have only this. See [The report record and the live log](https://docs.smartestqa.ai/en/report.html#testlog-vs-live-log).
- **Attempt:** One execution of one test case inside a run. Data rows and automatic retries each add an attempt, which is why a Result can say 5/6 for three test cases. See [Result chip](https://docs.smartestqa.ai/en/report-numbers.html#result-chip).
- **AI verdict:** The AI’s classification of a failed step: Real Bug, Test / Infrastructure Issue, Flaky or Unclassified, with a confidence. See [Verdicts](https://docs.smartestqa.ai/en/report-ai-analysis.html#verdicts).
- **InSight:** The home dashboard. **Execution** shows how runs went in a period; **Test Health** shows how much of the application the tests prove: requirement, scenario, risk and action coverage. See [InSight](https://docs.smartestqa.ai/en/insight.html).

## Auto-heal and Maintain

When every locator of an action fails, the runner looks for the element again. If it finds one clear match, it writes the new locator to the action at once, so the run goes on and every test that uses the action is fixed. Each repair waits as a card in **Maintain** › **Auto-heal** until a person approves or rejects it; rejecting puts the old locators back. The runner refuses to heal when the app itself looks broken, so real bugs still fail.

- How it decides, and when AI is involved: [How auto-heal decides](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html).
- Reviewing repairs: [Auto-heal reviews](https://docs.smartestqa.ai/en/maintenance-auto-heal.html).
- Turning passed AI steps into normal actions: [AI Steps](https://docs.smartestqa.ai/en/maintenance-ai-steps.html). Turning captured browser calls into an API test: [Network Calls](https://docs.smartestqa.ai/en/maintenance-network-calls.html).
- Project types: web steps are repaired; desktop steps only by the AI; mobile steps are not repaired today. See [Project types](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#project-types).

## Tasks and deploys

- **Task:** One item of work on a Kanban board, such as a defect. With [**Auto Task Creation**](https://docs.smartestqa.ai/en/tasks-from-runs.html#which-setting) on, a failed pipeline run creates a task with the failed steps and a link to the report. Tasks can sync with Jira or Azure DevOps. See [Tasks](https://docs.smartestqa.ai/en/tasks.html) and [Tasks from failed runs](https://docs.smartestqa.ai/en/tasks-from-runs.html).
- **Task status:** The board column: Open, In Progress, Resolved, Closed, plus statuses your company adds. Statuses are shared by all projects. See [Statuses](https://docs.smartestqa.ai/en/tasks-statuses.html).
- **Deploy:** A record your CI sends when a version reaches an environment. SmartestQA shows which version runs where and whether a pipeline tested it. See [Deploys & Repos](https://docs.smartestqa.ai/en/deployments.html).

## AI features and MCP

AI is switched per project in **Project Panel** › [**AI Options**](https://docs.smartestqa.ai/en/project-settings-ai.html): [**Enable AI**](https://docs.smartestqa.ai/en/project-settings-ai.html#enable-ai) turns it on, and one switch per capability turns each feature on or off. The project uses SmartestQA’s AI account or your company’s own provider key. See [AI Options](https://docs.smartestqa.ai/en/project-settings-ai.html).

| Where | What the AI does | Explained in |
| --- | --- | --- |
| Discover | Names controls and helps pick locators while you record. | [Discover Your App](https://docs.smartestqa.ai/en/discover-your-app.html) |
| Analyze | Turns documents into requirements and scenarios; scores requirements. | [AI wizard](https://docs.smartestqa.ai/en/analyze-import.html), [Assessment](https://docs.smartestqa.ai/en/analyze-assessment.html) |
| Automate | Writes steps from a prompt, expands a case into variations, writes code; AI steps act and check in plain words. | [AI in Automate](https://docs.smartestqa.ai/en/automate-ai.html), [AI steps](https://docs.smartestqa.ai/en/automate-steps-ai.html) |
| Report | Classifies failed steps and reviews a whole run. | [AI failure analysis](https://docs.smartestqa.ai/en/report-ai-analysis.html) |
| Maintain | Chooses the element when a locator repair needs it. | [How auto-heal decides](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html) |
| Agents | Autonomous agents work on a rhythm or after a deploy and leave reports and proposals; nothing is applied without a click. | [Autonomous Agents](https://docs.smartestqa.ai/en/ai-agents.html) |
| Your AI assistant | Claude or another MCP client works in SmartestQA in a chat. Every change is shown as a diff first and written only after you approve it. | [MCP & AI assistants](https://docs.smartestqa.ai/en/mcp.html), [Safe changes](https://docs.smartestqa.ai/en/mcp-safe-changes.html) |

What is sent to the AI provider is listed on each module’s FAQ, for example [Discover](https://docs.smartestqa.ai/en/discover-faq.html#faq-data) and [MCP](https://docs.smartestqa.ai/en/mcp-faq.html#faq-data).

## Roles and administration

| Role | Can | Cannot |
| --- | --- | --- |
| Admin | Everything in the company: projects, users, Project Panel, Company Settings, Integrations, Logs. | Assign Super Admin. |
| User | Test work in the projects they were given: Discover, Analyze, Automate, Schedule, Report and the rest of the main menu. | Create projects or users; open Project Panel, Company Settings, Integrations or Logs. |
| Super Admin | SmartestQA operators only. | Not a customer role. |

Item by item: [Roles & permissions](https://docs.smartestqa.ai/en/company-settings-roles.html#matrix). Every change, from the app, MCP or an API key, is recorded in the [audit log](https://docs.smartestqa.ai/en/logs.html).

## Related

- [Glossary](https://docs.smartestqa.ai/en/glossary.html): every term you meet on screen, A to Z.
- [Quick Start](https://docs.smartestqa.ai/en/quick-start.html): from sign-up to a first report in about 15 minutes.
- [Troubleshooting](https://docs.smartestqa.ai/en/troubleshooting.html): find your problem by symptom.
