📦 Workspaces

Workspaces represent the highest level of organization in Loopstack’s hierarchy, serving as isolated containers that group related pipelines and workflows while enforcing data boundaries and access controls.

Overview

A workspace acts as a logical boundary that encapsulates your automation projects. Think of workspaces as separate “projects” or “environments” where each contains its own set of pipelines, workflows, data, and access permissions.

workspaces:
  - name: content_automation
    title: "Content Automation Workspace"
    description: "Handles all content generation and processing workflows"
 
  - name: data_analysis
    title: "Data Analysis Workspace"
    description: "Contains analytics and reporting pipelines"

Hierarchical Structure

Workspaces sit at the top of Loopstack’s organizational hierarchy:

Every root pipeline, which is the starting point of an automation, is assigned to a workspace:

pipelines:
  - name: blog_generation_pipeline
    title: "Blog Generation Pipeline"
    type: root
    workspace: content_automation           # References the workspace
    sequence:
      - workflow: research_topic
      - workflow: generate_content
      - workflow: review_content

Data Encapsulation

Workspaces enforce strict data boundaries. Pipelines, workflows and their tools can only access data that exists within their assigned workspace, preventing accidental data leakage between projects.

Data isolation ensures:

• Security: Sensitive data in one workspace cannot be accessed by workflows in another
• Organization: Clear separation of concerns between different projects
• Debugging: Issues in one workspace don’t affect others
• Compliance: Easier to maintain data governance and audit trails

User Interface Organization

Workspaces provide structure in Loopstack Studio, making it easier to navigate and manage complex automation projects.

Studio Navigation

Loopstack Studio
├── Workspace: Content Automation
│   ├── Pipeline: Blog Generation
│   ├── Pipeline: Social Media Posts
│   └── Pipeline: Content Review
├── Workspace: Data Analysis
│   ├── Pipeline: Sales Reporting
│   ├── Pipeline: User Analytics
│   └── Pipeline: Performance Metrics
└── Workspace: Customer Support
    ├── Pipeline: Ticket Classification
    └── Pipeline: Response Generation

This organization allows teams to:

• Focus on specific projects without distraction
• Assign different team members to different workspaces
• Track execution history per workspace
• Monitor resource usage by project

Permissions and Access Control

Workspaces enable fine-grained access control, allowing you to restrict access to resources, files, APIs, and external services on a per-workspace basis.

Note: Permission and Access Control features are not yet implemented in the current version of Loopstack.

Configuration Examples

Basic Workspace Setup

workspaces:
  - name: blog_automation
    title: "Blog Automation"
    description: "Automated blog content generation and publishing"
 
pipelines:
  - name: daily_blog_pipeline
    title: "Daily Blog Generation"
    workspace: blog_automation
    type: sequence
    sequence:
      - workflow: research_trending_topics
      - workflow: generate_blog_post
      - workflow: schedule_publication

Multi-Environment Setup

workspaces:
  - name: development
    title: "Development Environment"
    description: "Testing and development workflows"
 
  - name: staging
    title: "Staging Environment"
    description: "Pre-production testing"
 
  - name: production
    title: "Production Environment"
    description: "Live customer-facing workflows"
 
# Same pipeline configuration can exist in multiple workspaces
pipelines:
  - name: content_generation
    workspace: development
    # Development configuration...
 
  - name: content_generation
    workspace: production
    # Production configuration with different permissions...

Best Practices

Logical Grouping: Group related pipelines that work with similar data or serve the same business function.

Environment Separation: Use separate workspaces for development, staging, and production environments.

Permission Principle: Follow the principle of least privilege - only grant access to resources that are actually needed.

Naming Convention: Use clear, descriptive names that indicate the workspace’s purpose and scope.

Documentation: Always include meaningful descriptions to help team members understand each workspace’s purpose.

Next Steps

With workspaces configured, you can proceed to define the pipelines that will execute within them. Pipelines coordinate the execution of workflows and define the automation logic for your specific use cases.

Continue to Pipelines →