Managing Projects
Step-by-step guide to configuring project settings, adding members, and setting up defaults for a Qualflare project.
Managing Projects
A project is where your test cases, launches, and defects for a specific product, component, or team live. This guide covers configuring an existing project. Your first project is created for you during the sign-up onboarding flow — there isn't a separate "create additional project" flow documented yet, so if you need a new project beyond your first, check Workspace Settings or contact your workspace administrator.
This guide follows the field names and actions documented in the Project Settings reference. If a button label or menu location has changed in the app since this was written, the reference page is the more likely to be current — please report any mismatch.
Workflow 1: Configure Project Basics
Steps
- Navigate to the project, then click Settings in the left sidebar.
- Under General Settings, set:
- Project Name — the display name shown in selectors and reports
- Project Key — a short, unique identifier (uppercase letters/numbers/underscores, 2-10 characters) used by the CLI and API, e.g.
qf login webapp <token>thenqf webapp collect results.xml - Description — optional context shown on the project overview
- Default Environment — the environment pre-selected when creating new launches
- Click Save Changes.
Workflow 2: Add Members to a Project
Steps
- Go to Project Settings → Members.
- Click Add Member.
- Select one or more workspace members not already in the project.
- Choose a project role: Admin (full project control), Member (create/edit tests, runs, defects), or Viewer (read-only).
- Click Add.
Project roles override the workspace-level role for that specific project — a workspace Member can be made a project Admin, and vice versa.
Workflow 3: Set Project Visibility
Steps
- Go to Project Settings → Members.
- Choose Open to Workspace (any workspace member can view) or Invite Only (only explicitly added members can access).
Use Invite Only for confidential projects, beta programs, or client-specific work.
Workflow 4: Configure Test Defaults
Steps
- Go to Project Settings → Test Configuration.
- Set the Default Test Priority applied to new test cases.
- Optionally configure Tagging Requirements (require at least one tag, or specific tag categories) and custom Automation Status labels.
- Optionally create a Test Case Template with pre-filled defaults for priority, automation status, tags, and step structure.
Workflow 5: Archive or Delete a Project
Steps
Archive (reversible):
- Go to Project Settings → Advanced.
- Click Archive Project and confirm.
An archived project keeps all data in read-only mode and can be unarchived any time from workspace settings.
Delete (irreversible, workspace Owners only):
- Go to Project Settings → Advanced → Danger Zone.
- Click Delete Project.
- Type the project name to confirm, then click Permanently Delete.
All launches must be completed or cancelled first. Deletion removes every test case, suite, launch, defect, and milestone in the project.
Related
- Project Settings Reference — full settings, member, and billing reference this guide is based on
- Projects Concept — what a project is and how it fits into a workspace
- Workspaces — the parent container for projects
Using Qualflare in Claude Code
Install the Qualflare plugin for Claude Code, run first-time setup, generate tests, upload results, and fix failures — all from the chat window.
Account Security
Secure your Qualflare account with two-factor authentication, session management, connected OAuth accounts, and password management.