Workspaces
Organize your data pipelines with isolated workspaces and control who has access to what.
Overview
Workspaces provide complete isolation and governance within Supaflow. Each workspace has its own datasources, pipelines, projects, and schedules. This allows you to control access—for example, give only your SOC team access to production workspaces while development teams work in separate spaces.
Every resource (pipeline, datasource, project) belongs to exactly one workspace, ensuring clean separation and controlled access.
Key capabilities:
- Create workspaces for different environments (dev, test, stage, prod)
- Switch between workspaces easily
- Share workspaces with team members
- Control access with owner, editor, and viewer roles
- Deploy configurations between workspaces
To access: Navigate to Workspaces in the sidebar.
Understanding Workspaces
What is a Workspace?
A workspace is an isolated environment for your data pipelines. Think of it like a project or environment where all your datasources, pipelines, and schedules live together.
Common workspace setups:
- Separate workspaces for dev, staging, and production
- One workspace per team (Marketing, Finance, Engineering)
Active Workspace
The active workspace is the one you're currently working in. This determines what you see in the Pipelines, Sources, Destinations, and Activities pages.
You can see your current workspace in the top navigation bar with its environment badge.
Environment Labels
Workspaces can be labeled with an environment type (dev, test, stage, uat, prod) for organization.
Note: Environment labels are for organization only - all workspaces have identical capabilities. The label just helps you visually identify the workspace's purpose.
Access Levels
Workspaces have three access levels:
| Level | What You Can Do |
|---|---|
| Owner | Full control - edit, share, delete workspace, manage all resources |
| Editor | Create and edit resources (pipelines, projects, datasources) |
| Viewer | Read-only access to all resources |
Creating a Workspace
Who can do this: Organization admins only
To create:
- Go to Workspaces in the sidebar
- Click + Create Workspace (top right)
- Enter workspace details:
- Workspace Name - Descriptive name (e.g., "Marketing Production")
- API Name - Auto-generated lowercase identifier (can customize)
- Description - Optional notes about the workspace's purpose
- Environment - Choose dev, test, stage, uat, or prod
- Click Create Workspace
You'll be redirected to the Workspaces list where your new workspace appears.
Good naming examples:
- "Marketing Production"
- "Engineering Dev"
- "Customer ABC - Prod"
Poor naming examples:
- "Workspace 1"
- "Test"
- "New"
Switching Between Workspaces
- Navigate to Workspaces in the sidebar
- Click the workspace card you want to enter
- The page refreshes showing that workspace's resources
The active workspace persists when you refresh the page or return to Supaflow later.
Best practice: Always verify the workspace badge in the top navigation before making changes.
Managing Workspaces
Editing a Workspace
Who can do this: Owners and Editors
To edit:
- Find the workspace card
- Click the three-dot menu (•••)
- Select Edit
- Update the name, API name, description, or environment
- Click Update Workspace
Note: Changing the API name may break existing API integrations.
Sharing a Workspace
Who can do this: Owners only
To share:
- Find the workspace card
- Click the three-dot menu (•••)
- Select Share
- Enter team member's email address
- Select their access level:
- Owner - For workspace administrators (1-2 people recommended)
- Editor - For data engineers building pipelines
- Viewer - For stakeholders, analysts, business users
- Click Send invitation
Managing access:
- View all team members with access
- Change someone's role
- Remove someone's access
Best practice: Review workspace access quarterly and remove inactive users.
Deleting a Workspace
Who can do this: Owners only
To delete:
- Find the workspace card
- Click the three-dot menu (•••)
- Select Delete
- Review what will be deleted (pipelines, projects, datasources, etc.)
- Type the workspace name to confirm
- Click Confirm Delete
⚠️ Important:
- Deletion is permanent and cannot be undone
- All resources are deleted (pipelines, datasources, projects, schedules)
- Activity history is preserved for audit purposes
Common Workspace Patterns
Pattern 1: Three-Tier Environment Setup
Separate dev, stage, and prod workspaces for safe deployments.
Workflow:
Dev (build) → Stage (test) → Prod (deploy)
Pattern 2: Team-Based Workspaces
Give each team their own workspace (Marketing, Finance, Engineering) for independent work with customized access controls.
Troubleshooting
API Name Already Exists
Problem: Can't create/edit workspace due to duplicate API name.
Solution: API names must be unique. Use a more specific name (e.g., marketing_dev instead of dev) or let the system auto-generate from your workspace name.
Best Practices
- Set appropriate access levels - Give Owner role to workspace admins only (1-2 people), Editor to data engineers, and Viewer to stakeholders
- Use the description field - Document what the workspace is for and who owns it
- Review access regularly - Remove users who left the team, downgrade access when responsibilities change
Related Pages
- Deployments - Promote pipelines between workspaces
- Projects - Organize pipelines within a workspace
- Settings - Organization and workspace settings
Support
Need help with workspaces? Contact us at support@supa-flow.io