Projects

What is a project

A project holds all the testing work for a specific application or service. Your tests, tasks, test runs, environment configuration, and team assignments all live under a project.

Most teams create one project per application they are testing. For example, if your company has a customer-facing web app and an internal admin dashboard, you would typically create two separate projects for those.

Project settings

Open your project and click the Settings tab. You need to be an organization owner, admin, or project admin to view and change settings. Regular project members and viewers don't see this tab.

General settings

The top section lets you edit the project name (what your team sees in the sidebar), a description summarizing what the project covers, and the default environment that gets pre-selected when creating tasks or test runs. Most teams set the default to staging or test.

Click "Edit" to modify these fields, then "Save" to apply. Changes take effect immediately.

Environment configuration

Below the general settings, you'll find the environment configuration section. This is where you manage environment variables and secrets for each of your four environments (development, test, staging, production). See the Environment configuration page for details.

Jira configuration

If your organization has Jira connected, a Jira Configuration card appears in project settings. This is where you set the JQL filter for the project and manage the knowledge agent.

Environments

Each project supports four environments. These represent the different stages where your application runs and where tests can be executed:

• Development: for local or early-stage environments where features are being built. Useful for quick validation during development.
• Test: a dedicated testing environment, often used for integration testing or QA team workflows.
• Staging: a pre-production environment that mirrors production as closely as possible. Ideal for final validation before releases.
• Production: the live environment. Use this for smoke tests, monitoring, or verifying deployments after release.

When you create a task or start a test run, you select which environment it should run against. This ensures tests are executed in the right context with the appropriate configuration.

Environment variables and secrets

Projects support environment-specific configuration through variables and secrets. These are managed from the project's Settings tab under the environment configuration section.

Environment variables are key-value pairs that the AI agent can use during test execution. For example, you might set a BASE_URL variable for each environment so tests automatically target the correct URL. Variables are visible to project members and can be updated at any time.

Secrets work similarly but are encrypted and cannot be viewed after creation. Use secrets for sensitive values like test account credentials or API keys. If you need to change a secret, you delete the existing one and create a new one.

Team access

Projects inherit the team from your organization, but you can control which members have access to each project. From the project's Members tab, you can assign or remove organization members.

This is useful when your organization has multiple teams working on different applications. Each team only sees and works with the projects relevant to them. Organization owners and admins always have access to all projects.

For more on how organizations and roles work, see the Organizations and teams page.