System Configuration

Configure organization identity, execution defaults, AI behavior, viewports, storage, imports, and operational settings in ContextQA.

Who is this for? Organization administrators and QA platform owners who manage workspace-wide defaults, evidence storage, and configuration safety.

ContextQA groups organization-wide controls under Settings. Changes on these pages can affect every test author and execution in the organization, so record the reason for a change, test it in a controlled workspace, and use the system audit trail when reviewing configuration history.

Organization settings

Open Settings → Organization Setting (/settings/organization_setting). The page provides navigation for Company Information, Test Execution, AI Configuration, Notifications, and Viewport.

ContextQA Organization Setting page showing company information, execution defaults, AI configuration, notifications, and viewport navigation

Company information

• Set the organization name displayed in the portal.
• Upload a PNG, JPG, or JPEG company logo within the displayed size limit.
• Prefer a transparent, light logo that remains readable in the sidebar.
• Select Save Settings only after reviewing the preview and the other changed fields.

Test execution defaults

The current page includes controls for:

• default browser;
• test-case and crawl timeouts;
• failed-step retry count;
• locator wait and automatic wait duration;
• all-step screenshot capture;
• video recording;
• autonomous crawl;
• default viewport and resolution;
• organization time zone.

These are defaults, not universal pass criteria. Test plans and environment-specific requirements may need a different browser, viewport, or timeout. Increasing a timeout can hide a performance problem, so investigate slow behavior before changing the organization default.

AI configuration

Select AI Configuration to review the default AI action, AI smartness mode, knowledge-base selection, metadata behavior, and Mock API Testing availability.

ContextQA Organization Setting AI Configuration section showing the default AI action, smartness mode, knowledge-base selector, AI metadata, and Mock API Testing

Use these controls to establish an organization baseline:

• Default AI Action determines whether the workspace creates steps directly or follows another configured review behavior.
• AI Smartness selects the default generation and execution profile.
• Default Knowledge Base supplies shared application context when one is selected.
• Use AI Metadata controls whether saved metadata contributes to AI context.
• Mock API Testing records and replays approved API responses when the capability is enabled.

Review generated or healed behavior after changing an AI default. A setting that helps one application may introduce unnecessary interpretation in another.

Notifications and viewports

The Notifications section accepts weekly report recipients. Use team-owned distribution addresses and avoid entering personal or customer addresses unless the organization has approved that use.

The Viewport section stores reusable mobile, tablet, laptop, and desktop resolutions. Choose viewports from supported-user data and product requirements. Remove obsolete configurations so test-plan authors do not select them accidentally.

Storage configuration

Open Settings → Storage (/settings/storage). The current catalog exposes Amazon S3 and Azure Cloud storage options; enabled providers show an active switch and a View Details action.

ContextQA Storage page showing Amazon S3 and Azure Cloud artifact-storage options

Storage configuration controls where screenshots and other execution artifacts are written. Before enabling a provider, confirm:

• bucket or container ownership and region;
• encryption and retention policy;
• service-account permissions;
• network access from the ContextQA deployment;
• lifecycle and deletion behavior;
• incident and credential-rotation ownership.

Storage detail panels can contain access credentials. Never include those values in screenshots, documentation, support tickets, or test steps. Store and rotate them through the organization's approved secret-management process.

Imports and exports

Open Settings → Imports and Exports (/settings/backups). The page lists available backup/import packages and provides an Import action. A new workspace may show the empty state There are no Backups created.

ContextQA Imports and Exports page showing the Import action and an empty backup list

Before importing a package:

1. Confirm that it belongs to the intended organization and workspace.
2. Record its source, creation date, and owner.
3. Review whether the import can replace or duplicate existing test assets.
4. Run the import in a controlled workspace when the package has not been validated.
5. Verify the resulting tests, plans, environments, and data before using them as a release gate.

The actions displayed on this page depend on deployment configuration and permissions. Do not assume that scheduled backup, export, or restore controls are available when they are not shown in the current workspace.

Related administration controls

• Team Management — users, organizations, and workspace membership
• Roles & Permissions — least-privilege role configuration
• Authentication — login modes and API credential safety
• Environment and data management — environment variables, databases, profiles, and global data