Project Settings

This page lists every tab and setting of a Qualflare project, with the role each one needs: General, Notifications, AI Features, Quality, Environments, Webhooks, Users and Access Tokens.

Accessing Project Settings

1. Navigate to the desired project
2. Click Settings in the left sidebar
3. Pick a tab: General, Notifications, AI Features, Quality, Environments, or Webhooks, or, under Access, Users or Access Tokens

Every project member can open Project Settings. What you can change depends on your role:

A plain "Editor or higher" or "Maintainer or Owner" means your access in this project: the higher of your project role and your workspace role. Your project role is the role you hold in this project itself. Where a row says "In the web app today", the app checks only your project role, so a higher workspace role doesn't turn those controls on. See How workspace and project roles combine.

General Settings

The General tab holds the project's name, identifier, description, domain and platform, the public report (Open Source plan), and the Delete Project card.

Project Name

The display name for your project. Appears in the project selector, headers, and reports.

• Field: Text input, at least 3 characters
• Locked: For a project linked to a GitHub repository (Open Source plan), the name follows the repository and can't be edited
• Update: Click Save Project to apply

Project Identifier

The project's URL slug: app.qualflare.com/project/<project-identifier>.

• Format: Lowercase letters, numbers, and single hyphens, for example web-app
• Set: When you create the project. Qualflare fills it in from the project name, and you can edit it before you save. On the Open Source plan, the name and identifier come from the repository you pick
• Unique: No two active projects in Qualflare can share an identifier
• Read-only: You can't change the project identifier after creation

Access tokens belong to one project, so the CLI doesn't use the Project Identifier. See Using Tokens with the CLI.

Description

What the project is about. Required. Qualflare uses it to personalize the project's AI features.

Project Domain and Platform

• Project Domain: SaaS, E-commerce, Finance, Healthcare, Education, or Other
• Platform: Mobile, Web, Game, API, or Embedded

Every new project starts with four environments: Development, Staging, Production, and QA. Manage them on the Environments tab. See Environments.

Public Report

Publish a world-readable report page for this project. The section shows for projects in workspaces on the Open Source plan, and, with only Unpublish, for a project that is still public after its workspace leaves the plan.

• Field: Toggle
• Default: Off
• When on: The report is live at reports.qualflare.com/p/<project-identifier>/launches, and a README badge/banner become available on the same panel. The report shows only launches uploaded while it is on.
• When off: The report goes offline, and the runs it showed stay hidden even if you publish again. Your project's launches and results are not affected. Cached pages can stay visible for up to about an hour.

See Open Source → Publishing a Report for the full walkthrough, including the badge/banner embed snippets.

Members and Permissions

Manage who works in this project on the Users tab.

Project vs Workspace Permissions

Your access in a project is the higher of your project role and your workspace role, so a project role can raise access but never lower it, and demoting someone's workspace role doesn't remove a higher project role. For examples, and for how the web app treats project roles today, see How workspace and project roles combine.

Project Roles

Projects use the same five roles as the workspace, and the person who creates a project gets the Owner role in it. For what each role can do, see Roles at a glance.

Inviting people needs the Maintainer or Owner role in the workspace, whatever your project role.

Invite Users

Add people to this project by email:

1. Click Invite User
2. Enter their Email Address
3. Click Send Invite

The invitee joins as a Viewer. If they weren't in the workspace yet, they join it as a Guest and see only the projects they're invited to. Invite links expire after 24 hours. Resend or revoke a pending invitation from its row's ⋯ menu. For the full how-to, see Invite people to a project.

Project Member List

Columns:

• Name: Member's display name
• Email: Email address
• Status: Active, or Pending for an invitation not yet accepted
• Role: Project role
• Date Added: When they joined the project

The list shows people who hold a role in this project. Workspace members who only inherit access through their workspace role aren't listed.

Use a row's ⋯ menu to Promote or Demote someone one step (Viewer → Editor → Maintainer), or to Remove them from the project.

Who Can See This Project

There's no visibility setting. A workspace role from Viewer up applies in every project in the workspace. In the web app today, though, the Projects page lists only the projects someone is a member of, so a workspace member who isn't in this project doesn't see it there. Invite them to give them access (see How workspace and project roles combine). To give an outside collaborator access to this project only, invite them from this page: they join the workspace as a Guest. To publish launch history publicly, see Public Report.

Quality Settings

Configure flaky-test detection and quality targets for this project, under Project Settings > Quality.

Qualflare checks a test case again each time you upload a launch that contains it. It takes the case's most recent results, one per launch, and flags the case as flaky when it both passed and failed, has enough results, and the less common result makes up at least the Minority Threshold. Failed, error, timeout and aborted results count as failures. Skipped and pending results are ignored.

When a case is flagged, Qualflare opens a defect for it with the flaky category (shown as Flakiness, and as Flaky Test in the Category filter), and closes it when the case stops being flaky. A single case run that passed only after a retry is also marked flaky, whatever these settings say.

Tuning guidance:

• A smaller window reacts faster to recent behavior but is noisier on low-frequency test suites.
• Raising the minority threshold makes detection stricter — only cases with more balanced pass/fail flips get flagged.
• These settings only affect flaky classification; they don't change how tests run.

Flaky classification feeds the flaky score on a flagged test case's badge. See Identify Flaky Tests. Where enabled, it also feeds AI Insights recommendations.

Quality Targets

Set per-project targets that the project dashboard shows: Target Success Rate, Target Flake Rate, and Target Automation Rate (percentages), and Target Launch P90 Duration (seconds). Leave a target empty or set it to 0 for no target.

Notifications

The Notifications tab has three groups.

Your Email Notifications

One switch that turns this project's emails on or off for you only. Other members are unaffected.

The switch currently saves only for members with a workspace role of Editor or higher. If it doesn't change for you, use the one-click Unsubscribe option your mail app shows on any email from this project.

Project Email Notifications

Project-wide email switches. Changing them needs a workspace role of Editor or higher; other members see them read-only.

Insight Notifications

In-app alerts for case optimization insights: Flaky Case Insights, Low-Value Case Insights, and Redundant Case Insights.

Webhook Events

Webhooks are set per project under Project Settings > Webhooks. There are no workspace-level webhooks. See Webhooks for the events, payload, and signature.

Slack Channels

Slack notifications for a project are set under Integrations in the project sidebar, where you pick the Default Channel and the events. See Slack.

Advanced Settings

There's no Advanced tab. Delete Project is on the General tab, and projects can't be archived (test cases and suites can).

Project Deletion

Owner · workspace (requires the Owner role in the workspace)

Prerequisites:

• The Owner role in the workspace and in this project. The card shows only to the project's Owner, and only a workspace Owner's deletion succeeds

What you lose access to:

• All test cases and suites
• All launches and results
• All defects
• All milestones
• Project settings and configurations
• The project's member list (workspace membership stays)

Deletion Steps:

1. Open Project Settings > General
2. Scroll to the Delete Project card at the bottom
3. Click Delete Project
4. Type the project identifier to confirm
5. Click Delete Project

For the step-by-step guide, see Delete a project.

Data Retention

There is no retention setting, and retention is the same on every plan. Test cases, suites, launches and results don't expire: Qualflare keeps them until someone deletes them. Files you attach to a test case in the app are kept the same way.

Qualflare deletes these automatically, on every plan:

Trend charts show at most the last 90 days. Only the chart history ages out: your launches and results stay.

Related

• Create and manage projects: the step-by-step guide to a project and its settings
• Workspaces and Workspace Settings: workspace-level configuration
• Roles and permissions: role permissions and inheritance
• Invite and manage users: invitations and role changes
• Project teams: group project members into teams
• Open Source: the full Open Source plan walkthrough
• Milestones: milestone configuration and usage
• Test Cases: test case configuration options