Skip to main content

Workspaces and projects

A Qodex project is one app or service you are testing. It contains the agent chats, saved scenarios, scripts, findings, run history, memory, environments, auth profiles, integrations, and API keys for that app. A workspace is the set of projects your team can access from the project switcher.

Project boundary

Use one project per app or service. If you test two unrelated apps, create two projects. If you test staging and production for the same app, keep them in one project and use separate environments. Nothing should cross a project boundary unless you explicitly configure it. That keeps findings, memory, credentials, repositories, and usage separated.

What lives in a project

AreaWhat it contains
Agent chatsConversations with Qodex and the decisions made during testing.
Scenarios and scriptsReusable API, UI, security, and run-test assets.
Test runsExecution history, status, artifacts, and results.
FindingsConfirmed issues with severity, evidence, and triage state.
Memoryproject.md, discoveries, constraints, and reusable context.
EnvironmentsBase URLs, auth profiles, and target-specific settings.
CatalogsImported endpoints, crawled pages, and collections.
IntegrationsGitHub repos, Slack/webhook notifications, BYOK keys, and related setup.
MembersProject admins and members.
API keysKeys for CI, webhooks, and external triggers.
If multiple apps share one project, Qodex memory and findings can become confusing. Keep the boundary clean.

Create a project

1

Open the project switcher

Click the project name in the top bar.
2

Create the project

Choose Create project, enter a name, and add a short description.
3

Complete first-run setup

Give Qodex the app URL, staging credentials, app purpose, and any flows it should avoid. This becomes project memory for future runs.

Switch projects

Use the project switcher in the top bar. The URL changes to the selected project slug, and the app loads that project’s chats, scenarios, findings, settings, and integrations.

Archive a project

Project admins can archive a project from Settings > Danger zone > Archive project. Archived projects disappear from the switcher and stop accepting runs. Data is not permanently deleted by archiving. Permanent deletion is a separate gated action.

Roadmap

Workspace-level rollups are planned: cross-project activity, spend, findings, and admin visibility. Workspace-level SSO is also planned. Today, the project is the main operational boundary.

Next steps

Members and roles

Invite teammates and choose permissions.

Plans and pricing

See how plans apply to projects.

Projects concept

Learn why projects are the tenancy boundary.

BYOK

Configure provider keys per project.