Projects
Organize your pipelines and transformations within a workspace.
Overview
Projects group related data pipelines and transformations within your workspace. Each project connects to a warehouse datasource and can optionally integrate with a git repository for version control.
Hierarchy: Organization → Workspace → Project → Pipelines/Transformations
Key capabilities:
- Group related pipelines and transformations
- Connect to a warehouse datasource
- Optional git integration for version control
- Control access with owner, editor, and viewer roles
- Track pipeline counts and metrics
Project Types
| Type | Description | Status |
|---|---|---|
| Pipeline | Data ingestion and activation pipelines | ✅ Active |
| Transformation | Data transformation processes (dbt, SQL models) | 🔜 Coming Soon |
Only Pipeline projects are currently available. Transformation projects will be enabled in a future release.
Creating a Project
Who can do this: Organization admins, workspace owners and editors
Prerequisites: At least one active warehouse datasource (Snowflake, BigQuery, PostgreSQL, etc.)
To create:
- Navigate to Projects in the sidebar
- Click + New Project
- Fill in project details:
- Project Type - Choose Pipeline (Transformation coming soon)
- Project Name - Descriptive name (e.g., "Marketing Data Integration")
- API Name - Auto-generated lowercase identifier (can customize)
- Description - Optional notes about the project's purpose
- Warehouse Datasource - Select the warehouse for this project
- Git Integration (Optional):
- Repository URL (e.g.,
https://github.com/myorg/repo.git) - Branch name (e.g.,
main)
- Repository URL (e.g.,
- Click Create Project
You'll be redirected to the Projects list where your new project appears.
Managing Projects
Navigate to Projects in the sidebar to view all projects. Each project card shows the project name, warehouse datasource, git info (if configured), and pipeline counts.
Access Levels
| Level | What You Can Do |
|---|---|
| Owner | Full control - edit, share, delete project, manage pipelines |
| Editor | Edit project settings, manage pipelines, cannot share or delete |
| Viewer | Read-only access to project and pipelines |
Project Workspace
Click the Workspace button on a project card to open the project workspace, where you can create and manage all pipelines for that project. Pipelines created within a project automatically use the project's warehouse datasource.
Editing a Project
Who can do this: Owners and Editors
To edit:
- Find the project card
- Click the three-dot menu (•••)
- Select Edit
- Update name, description, warehouse datasource, or git settings
- Click Save
Note: Changing the warehouse datasource may affect existing pipelines.
Sharing a Project
Who can do this: Owners only
To share:
- Find the project card
- Click the three-dot menu (•••)
- Select Share
- Enter team member's email address
- Select their access level (Owner, Editor, or Viewer)
- Click Send invitation
Deleting a Project
Who can do this: Owners only
To delete:
- Find the project card
- Click the three-dot menu (•••)
- Select Delete
- Confirm deletion
⚠️ Important:
- Deletion is permanent and cannot be undone
- Review all pipelines in the project before deleting
- Project associations with pipelines may break
Common Project Patterns
Pattern 1: Single-Source Integration
Group all pipelines from one SaaS application (e.g., "Salesforce Integration") with ingestion pipelines, transformations, and activations all in one project.
Pattern 2: Multi-Source Integration
Combine data from multiple sources into a unified view (e.g., "Customer 360") with pipelines from Salesforce, HubSpot, Zendesk, and Stripe feeding into transformation tasks.
Troubleshooting
Cannot Create Project
Problem: Form won't save or required fields are missing.
Solution: Ensure Project Name, API Name, and Warehouse Datasource are filled. API names must be unique within the workspace.
Changing Warehouse Datasource
Problem: Want to change project warehouse but existing pipelines may break.
Solution: Create a new project with the desired warehouse, recreate pipelines, test, then delete the old project.
Best Practices
- Organize by business domain - Create one project per major data source or business domain (e.g., "Salesforce", "Customer Analytics")
- Set appropriate access levels - Give Owner role to project leads only (1-2 people), Editor to data engineers, Viewer to stakeholders
- Use the description field - Document what data the project handles and who owns it
- Configure git integration - Add repository URL and branch for version control and audit trail
- Separate dev and prod - Use different projects and warehouses for development and production
Next Steps
- Create Ingestion Pipelines - Build pipelines within your project
- Create Activation Pipelines - Push enriched data back to SaaS apps
- Create Tasks - Add SQL transformations to your project workflows
- Create Orchestrations - Chain pipelines and tasks together
- Deploy Projects - Promote projects across workspaces
Support
Need help? Contact us at support@supa-flow.io