Skip to main content

What is a Workspace?

A workspace in Blocks is an isolated space that includes:
  • Team Members - Users who can access and use Blocks in this workspace
  • Repositories - GitHub repositories connected to the workspace
  • Integrations - Platform connections (GitHub, Slack, Linear)
  • Agent Configurations - API keys, subscriptions, and agent configuration
  • Commands - Shared reusable prompts available to the team
  • Usage Quotas - API usage limits and billing information
  • Settings - Workspace-level configurations and preferences
Think of a workspace as a complete Blocks environment for a person or team.

Types of Workspaces

Blocks supports two types of workspaces:

Personal Workspaces

Automatically created when you sign up for Blocks. Characteristics:
  • ✅ Created automatically on signup
  • ✅ Free to use during beta
  • ✅ Perfect for individual developers
  • ✅ Full access to all Blocks features
  • ✅ Your own API keys and settings
  • ✅ Private repositories and sessions
Best For:
  • Individual developers
  • Personal projects
  • Learning and experimentation
  • Side projects

Organization Workspaces

Created for teams and organizations that want to collaborate. Characteristics:
  • 👥 Shared by multiple team members
  • 🔧 Centralized configuration and settings
  • 📊 Unified billing and usage tracking
  • 🎯 Team-wide commands and workflows
  • 🔐 Organization-level repository access
  • 📈 Admin controls and permissions
Best For:
  • Development teams
  • Companies and organizations
  • Shared projects
  • Team collaboration
Learn more: Organization Workspaces

What Workspaces Contain

Team Members (Multiple with organizations only)

  • Users who have access to the workspace
  • Members share access to connected repositories
  • All members can see and use workspace commands

Repositories

  • GitHub repositories the workspace has access to
  • All team members can work with these repos
  • Configured through GitHub App installation
  • Can be added or removed by workspace admins

Platform Integrations

Each workspace can connect to:
  • GitHub - For issue and PR interactions
  • Slack - For Slack channel integration
  • Linear - For Linear issue management
Integrations are workspace-specific and configured independently.

Commands

  • Workspace-level reusable prompts
  • Created by any team member
  • Shared across the entire workspace
  • Available on all platforms (Dashboard, Slack, GitHub, Linear)
Learn more: Commands

Usage and Billing

  • Usage quotas are tracked per workspace
  • API costs are based on your configured API keys and subscriptions
  • Blocks usage is free during beta
  • Future billing will be workspace-based

Switching Between Workspaces

If you’re a member of multiple workspaces, you can easily switch between them:
1

Open Workspace Switcher

In the Blocks Dashboard, click on the workspace name in the bottom left navigation sidebar
2

Select Workspace

Choose the workspace you want to switch to from the dropdown
3

Workspace Changes

The dashboard updates to show:
  • That workspace’s repositories
  • That workspace’s commands
  • That workspace’s sessions and history
  • Your settings for that specific workspace
Your sessions, settings, and commands are specific to each workspace. Switching workspaces changes your entire context.

Workspace Isolation

Important characteristics of workspace isolation:
  • Sessions are isolated - Sessions in one workspace don’t affect another
  • Settings are separate - Each workspace has independent configurations
  • API keys and subscriptions are per workspace - Authentication is shared in workspaces
  • Commands are shared - Within a workspace, commands are available to all
  • Repositories are workspace-level - Connected repos are accessible to all members

Common Workspace Scenarios

Scenario 1: Individual Developer

Setup:
  • Use your personal workspace
  • Connect your personal repositories
  • Configure your preferred agent
  • Create commands for your workflow
Benefits:
  • Complete control
  • Privacy for experiments
  • No coordination needed
  • Free during beta

Scenario 2: Team

Setup:
  • Contact founders to create an organization workspace
  • Invite team members
  • Connect shared repositories
  • Create team-wide commands
Benefits:
  • Shared access to repos
  • Consistent workflows via commands
  • Unified visibility
  • Centralized configuration

General Tips

  • 📋 Review workspace settings periodically
  • 🔍 Clean up (archive or delete) old sessions to stay organized
  • 🎯 Use appropriate workspace for each project
  • 👥 Communicate workspace changes to team members

Troubleshooting

Cause: Repository not authorized in GitHub installationSolution:
  1. Go to GitHub → Settings → Applications → Blocks
  2. Add the repository to your GitHub App installation
  3. Refresh Blocks dashboard
Cause: Not invited or no Blocks accountSolution:
  • Contact your workspace admin
  • Ask for invitation after you create a Blocks account

Next Steps