Projects

Group related pipelines or dbt Core models around the warehouse where the work runs.

Project Types

Project type	Use it for	What it includes
Pipeline	Ingestion and activation pipelines	Pipeline creation and management
Transformation	dbt Core models and commands	Project file editing, model preview, generated artifacts, and Git

A project keeps its type and datasource after creation. Create a separate project when work must use another project type or warehouse.

Create a Pipeline Project

1. Navigate to Projects
2. Click Create Project
3. Select Pipeline
4. Enter the project name, API name, and optional description
5. Select the warehouse destination for the project's pipelines
6. Click Create Project

Open the project to create and manage ingestion pipelines and activation pipelines.

Create a Transformation Project

1. Navigate to Projects
2. Click Create Project
3. Select Transformation
4. Enter the project name, API name, and optional description
5. Select a Snowflake, PostgreSQL, Amazon Redshift, Google BigQuery, or Databricks DBT Warehouse
6. Set dbt Target Schema / Namespace. This field is required for PostgreSQL. For other supported warehouses, leave it blank to use the datasource default or set it to a dedicated target
7. Choose Start from scratch or Import from Git
8. Click Create Project

Open the project to edit files, preview models, run dbt commands, and work with Git. See dbt Core transformations.

Target Schema or Namespace

A transformation project can override the datasource's default target location. Use this when each project should build into its own schema, dataset, or namespace.

For PostgreSQL, set the target schema because the datasource has no default schema for dbt. For other supported warehouses, leave the field blank to use the datasource default or set a project-specific target. Use a dedicated development target while evaluating a project because dbt commands can create or update warehouse objects. The datasource identity must be able to create and update the objects that the project builds in the selected target.

Manage Projects

The Projects page shows pipeline and transformation counts and provides filters for finding a project.

Open a project to manage its contents. Use the project menu to edit its name or description, share it, or delete it when your role permits the action.

Access Levels

Access	What it permits
Owner	Manage the project, access, and deletion
Editor	Edit project work and run supported operations
Viewer	Inspect the project without changing it

Git linked accounts remain personal. Sharing a project does not share your Git credentials with another member.

Organize Projects

Use a project boundary that makes ownership and deployment clear:

• One pipeline project per business domain or destination boundary
• One transformation project per dbt project and target environment
• Separate development and production projects when they use different warehouses or permissions
• Clear names and descriptions that identify the owning team and purpose

Troubleshooting

A datasource is not available

Problem: The warehouse you want is missing from the project form.

Solution: Project forms list eligible datasources from the current workspace. Confirm the datasource is active and supports the selected project type. Transformation projects list only datasources with dbt support. If the form reports No dbt warehouses available with required capabilities, switch to the workspace that contains the warehouse or create and test a supported datasource in the current workspace.

Project type or datasource cannot be changed

Problem: The edit form does not allow you to select another type or warehouse.

Solution: This is expected. Create a new project with the required type and datasource, move or recreate the work, test it, and then retire the old project.

Transformation project creation fails

Problem: Scratch initialization or Git import does not complete.

Solution: Test the selected warehouse connection. For a private Git import, confirm that the repository URL is correct and the linked account can read it. Public HTTPS repositories do not require an account.

Related Pages

• dbt Core transformations
• Create an ingestion pipeline
• Create an activation pipeline
• Linked Git accounts
• Deployments

Support

Need help? Contact us at support@supa-flow.io