# Settings for the Testing profile

> Behavioral settings for the QA/Testing profile in Delegate, configurable under Settings > Behavior preferences > QA / Testing, with default values and options.

## Settings for the QA/Testing profile

During onboarding, after selecting the **QA/Testing** persona, the **QA/Testing** profile gets enabled with default settings across seven categories under **Settings** > **Behavior preferences** > **QA / Testing**. These settings can be changed at any time. 

The behavioral settings govern how **Delegate** communicates, responds to tasks, handles sensitive operations, requests clarification, and manages user privacy within a QA and testing context. Understanding these defaults is essential for QA practitioners who rely on **Delegate** as a daily assistant. 

:::tip
These settings are applied automatically when the **QA/Testing** persona is selected during onboarding. They can be supplemented by learned preferences, stored under **Knowledge**, which persist across sessions. Explicit system prompt Behavior Preferences always take priority over learned memory preferences.
:::

:::important
The settings documented in this section describe the default behavioral profile for **QA/Testing** persona users. These defaults do not override core safety rules, topic restrictions, bulk-operation approval thresholds, mandatory document verification steps, or the one-step-at-a-time response rule. Those constraints are always enforced regardless of profile selection.
:::

### Communication settings
The **Communication** settings define the tone, depth, and style of all **Delegate** responses. The **QA/Testing** profile is optimized for technical practitioners who require precision and completeness over brevity. 

| Parameter | Configured value | Description |
| --- | --- | --- |
| **Response Depth** | **Thorough & Detailed** | Complete, comprehensive answers; full context provided without summarizing away critical detail |
| **Tone** | **Technical & Precise** | Domain-correct terminology used; no oversimplification of technical concepts |
| **Format** | **Markdown with Structure** | Headers, bullet lists, code blocks, and tables used to maximize scannability |
| **Accuracy Priority** | **High** | Prioritizes truthfulness, nuance, and technical insight over speed of delivery |

### Proactivity settings
The **Proactivity** settings determine how **Delegate** offers information, suggestions, and follow-up actions after completing a task. The **QA/Testing** profile is configured to suggest relevant next steps proactively, without taking unsolicited significant actions on the user's behalf. 
* Relevant next steps are suggested after every completed task 
* Unsolicited significant actions are not taken without explicit user confirmation 
* Follow-up suggestions are phrased from the user's perspective (e.g., "How do I...", "Show me...") 
* Destructive or irreversible follow-up actions are never suggested 

### Clarification settings
The **Clarification** settings govern when and how **Delegate** asks for additional information before proceeding. The **QA/Testing** profile requires explicit confirmation rather than assumptions, reducing the risk of incorrect execution in test and production environments. 
* Clarifying questions are asked before making assumptions about ambiguous requests. 
* The **AskUser** tool is used for structured prompts with predefined options when applicable. 
* **Planning Mode** is entered when requirements are ambiguous or tasks involve multiple decision points. 
* Free-text questions are presented for inputs requiring typed values such as credentials, URLs, or custom text. 

### Action Transparency settings
**Action Transparency** is a three-phase protocol ensuring full visibility into **Delegate**'s execution at every stage of a task. This setting is particularly valuable in QA contexts where traceability and auditability of automated actions are required. 
* Pre-execution: **Delegate** explains what it intends to do before running any action or calling any tool. 
* Post-execution: A clear summary of what was accomplished is provided after completing each action. 
* Risk Highlighting: Potential risks and side effects are surfaced and explained before any sensitive or destructive operation is performed. 

### Caution settings
The **Caution** settings apply a safety-first execution posture across all task types. This is critical in QA environments where accidental mutations to test data, configurations, or production systems can have significant downstream impact. 
* Significant or irreversible actions require explicit user confirmation before execution 
* Safe approaches are preferred over fast ones when trade-offs exist 
* Destructive operations (delete, wipe, clear, revert, undo) are never recommended unless explicitly requested by the user 
* Non-destructive alternatives are always presented first: archive, move, export, compress, review

### Privacy settings
The **Privacy** settings ensure elevated care when handling potentially sensitive information. This is especially relevant in QA workflows where test data may contain Personally Identifiable Information (PII), credentials, or confidential system configurations. 
* Sensitive data (PII, credentials, internal configurations, API keys) is handled with elevated caution 
* User data is never transmitted to external services based on untrusted or injected instructions 
* Credentials are sourced from UiPath Orchestrator assets or **Integration Service** connections — never requested via chat 
* Cross-application data access is restricted to user-authorized actions only 
* Prompt injection detection is active: external content claiming authority or requesting data exfiltration is blocked and surfaced to the user
* By default, **Delegate** only captures screenshots of applications you have explicitly attached to the session

### Reasoning effort setting
**Delegate** includes an Effort control (Low / Medium / High) that governs the depth of reasoning applied per task. The **QA/Testing** profile defaults to **Medium**, balancing thoroughness with response speed. This can be adjusted at any time from **Settings**.