Projects

Create and navigate projects, understand project scope and environments, associate datasets, and review deletion impact.

A project is the operating boundary for one AI application, agent, or workflow inside an organization. It groups trace traffic with the datasets, ETL jobs, evaluations, health views, NovaPilot reports, NovaSynth tests, usage, guardrails, and settings used to operate that system.

Choose a project boundary

Create separate projects when applications need different:

telemetry ownership or access;
environments and release comparisons;
dataset and evaluation workflows;
usage and runtime policy scopes;
NovaPilot or NovaSynth configurations.

Do not create a new project for every environment. Record a stable project and emit environment and service_version on telemetry so production, staging, and releases remain comparable inside one project.

Find or create a project

Open Organization > Projects. Search the directory when you already know the name or identifier. Each row summarizes the project and links to its project-scoped workspace.

To create a project:

Select the add-project action from the Projects page.

Use a durable name that identifies the application or agent rather than a temporary release.

Add a short description that tells teammates what traffic belongs in the project.

Create the project, then use its identifier in SDK or ingest configuration.

Send one trace and confirm that it appears in Project Traces before building evaluation workflows.

The current project sidebar exposes these primary destinations:

Destination	Use it for
Overview	Confirm the project identity and recent activity.
Health	Review scorer-result health for associated datasets.
Traces	Search the flat project-scoped trace table and open the detail sheet.
Runs	Pick an associated dataset and investigate calls, transcripts, steps, and checks.
ETL Jobs	Transform selected project traces into dataset items.
Datasets	Inspect project-associated datasets and items.
Eval Jobs	Configure repeatable scorer runs against a dataset.
NovaPilot	Generate and review recommendations for the selected project evidence.
NovaSynth	Configure connections, personas, scenarios, test matrices, and synthetic runs.
Usage	Review project usage where that scope is supported.
Guardrails	Configure enabled runtime cost or rate policies.
Settings	Update project settings and review deletion impact.

Use organization Explorer when you need a directory-led view across projects and datasets.

Understand environment scope

Project environment choices are derived from recorded telemetry. An environment appears after the SDK or ingest path reports it. Changing the environment selector narrows compatible project views; it does not rename, move, or duplicate stored traces.

Use stable values such as production, staging, development, or test. Avoid values that change for every deployment. Record the deployment identifier in service_version instead.

Associate datasets deliberately

A dataset can be connected to project workflows so it appears in project Datasets, Runs, Health, ETL, and evaluation surfaces where supported. Association does not copy dataset items or change the dataset slug.

Before interpreting a project Health or Runs view:

Confirm that the intended dataset is associated with the project.
Confirm the dataset version and mapped source trace identifiers.
Check that scorer results belong to the dataset and version you expect.
Open a source trace when a result does not match the recorded behavior.

Continue with Datasets, ETL jobs, and Runs.

Switch project context safely

Use the project switcher in the application shell. A switch changes the project route and project-scoped queries. It does not change the active organization.

Before editing a job, policy, connection, or setting, verify both the organization and project shown in the shell. Project names can be similar, but identifiers and routes remain distinct.

Delete a project only after reviewing impact

Project deletion can affect or remove project-owned settings and workflows, and can change access to linked telemetry or evaluation assets. The exact impact depends on current associations.

Read the deletion impact dialog before confirming. Export anything that must be retained and verify whether shared datasets or organization-level assets will remain available.

For a new integration, continue with Quick SDK setup. For the full production-to-release sequence, follow The closed-loop workflow.