Edit a project
The Projects screen
Section titled “The Projects screen”The Projects screen lists every project in a grid, grouped by folder. Each row shows the project name, its source connection, the number of workspaces, and when it was created. Select a project row to open it. Use the New project button at the top right to create one. Projects without a folder sort last, so folders render first and loose projects fall to the bottom of the grid.
Project details are edited inline on the Details tab of the project detail screen. There is no separate edit page: open the project, make your changes on the Details tab, and save without leaving the screen.
Opening the Details tab
Section titled “Opening the Details tab”Select a project row from the Projects screen. The project detail screen opens on the Details tab by default. If you were on a different tab, click Details to return to it.
Editing fields
Section titled “Editing fields”The Details tab is one form in five sections.
- Details holds Name, the display name for the project; Folder, the virtual folder path that groups it in the Projects list (see “Organizing projects into folders” below); and AI Context, a free-text description recorded on the project (see “AI Context” below).
- Connection holds Source connection, the connection the project reads from, and Target connection, the connection it writes to.
- Pipeline holds the catalog assignments for the project’s generated pipelines, drawn as a left-to-right diagram (see “Pipeline catalogs” below).
- Source options holds Record source, Record source name, Persist history, Dedupe source, and Ingest runtime. These travel with the project rather than with a single import, so they set the default shape of everything the project ingests.
- Deployment options holds Load notebooks from git, and, once that is on, Git repository URL, Git provider, Git branch, and Path root. This section appears only for projects whose target platform supports it.
Click into any field and change its value. Save and Cancel sit in the page header beside the tab strip, and become active as soon as you change something.
Organizing projects into folders
Section titled “Organizing projects into folders”The Folder field groups projects into a virtual folder hierarchy in the Projects list.
Type a path directly (for example, Finance/Reporting) or pick an existing path from the
suggestions. Folders are derived from the paths assigned to projects: a folder appears only
while at least one project sits in it, and you cannot create an empty folder. Folder paths
are case sensitive, so Finance and finance are separate folders. The folder is purely
organizational. It does not change the project’s name or where the project is stored in
version control, and moving a project between folders never renames anything. To take a
project out of its folder, clear the field; the project returns to the top level.
AI Context
Section titled “AI Context”The AI Context field records a free-text description of the project: its business purpose, the domain it covers, and any naming conventions that work on the project should follow. DeltaVault stores this context with the project, alongside the project’s other metadata, so it is captured in one place for AI-assisted work on the project. Write it the way you would brief a new team member on what the project is for. The field accepts any plain text and can be left blank.
Pipeline catalogs
Section titled “Pipeline catalogs”The Pipeline section shows the project’s pipeline as a left-to-right diagram of methodology layers, from the source layer through to the target layers. Each layer is a group with a catalog picker inside it, where you choose the catalog that the layer’s tables are generated into. You cannot drag or rearrange the diagram itself; its layout follows the project’s methodology.
Directional arrows connect each layer group to the next, pointing in the direction data flows, so you can read the pipeline from source to target at a glance. Each layer-group header also shows a platform icon for the connection bound to that layer: the source group shows the source connection’s platform, and every downstream group shows the target connection’s platform. If a layer has no connection bound, or its platform has no icon, the header shows no icon.
Saving and canceling
Section titled “Saving and canceling”- Save: persists your changes to the current branch. After a successful save, Save and Cancel disable again until you make another change.
- Cancel: discards your unsaved changes and reverts all fields to their last saved values. You stay on the Details tab; nothing is deleted.
Action buttons always read in the same order across screens: Save first, then Cancel, then any other actions, with less-common actions tucked into the three-dots overflow menu on the far right.
Both buttons are disabled when no changes are pending. If there are validation errors (for example, a missing required connection), Save stays disabled with a tooltip explaining why.
Switching tabs with unsaved changes
Section titled “Switching tabs with unsaved changes”If you navigate to another tab (Workspaces, Canvas, Templates, Build, or Validation) while the Details tab has unsaved changes, those changes are discarded. Use Save before switching tabs to keep your edits.
Adding a new connection mid-edit
Section titled “Adding a new connection mid-edit”The Source and Target connection dropdowns each have an Add new connection option. Selecting it takes you to the new-connection form and saves a snapshot of your current edits. When you return to the project after creating the connection, the Details tab restores your in-progress edits and pre-selects the newly created connection in the relevant dropdown.
Role and branch requirements
Section titled “Role and branch requirements”Editing project details requires the editor role and a feature branch. The fields and Save button are disabled for viewers and on the main branch, where everything is read-only. Switch to a branch to make changes.
Creating a new project
Section titled “Creating a new project”Creating a project is separate from editing one. Use the New project button at the top right of the Projects screen to open the project creation form. The creation form uses the same fields as the Details tab.
Delete a project
Section titled “Delete a project”Delete a project from its actions menu on the Projects screen, next to Edit.
Deleting a project removes its default workspace, and clears the project’s own model assignments and table links. If the project still has other workspaces besides its default one, the delete is blocked until you remove them first; the dialog tells you how many stand in the way.