Runwork
All Features

Workspaces

Isolated containers for team collaboration

Each workspace is a complete, isolated environment with its own apps, data, integrations, and team. Perfect for separating clients, projects, or departments.

Capabilities

Full Isolation

Each workspace has separate data, apps, and settings. No accidental cross-contamination.

Team Management

Invite team members to specific workspaces. Control who sees what.

Shared Data Layer

Within a workspace, all apps share the entity graph. Across workspaces, complete isolation.

Workspace Settings

Configure each workspace independently: integrations, branding, permissions.

Default Workspace

Every user gets a personal default workspace. Create more as needed.

Use Cases

Client separation (agencies) Department isolation Project sandboxes Dev/staging/prod environments

Why It Matters

How It Works

Workspaces are Runwork's isolation boundary—complete, separate environments for different teams, clients, or projects. Each workspace contains its own apps, entities, integrations, and team members. What happens in one workspace stays in that workspace.

Every user starts with a personal workspace, but you can create additional workspaces as needed. Agencies create workspaces per client. Enterprises create workspaces per department or project. Each workspace has its own settings, integrations, and data—complete isolation without complex configuration.

Within a workspace, the entity graph connects everything. Apps share access to common data like Customers, Orders, and Products. But across workspaces, there's no data leakage. Client A's data never mixes with Client B's data, even if they're managed by the same agency.

Team members are invited to specific workspaces with defined permissions. Someone can be an admin in one workspace and a viewer in another. This enables flexible collaboration—bring in contractors for a specific project without giving them access to your entire organization.

Frequently Asked Questions

What is a workspace in Runwork?
A workspace is an isolated environment containing apps, data, integrations, and team members. Workspaces provide complete separation between different contexts—clients, projects, departments, or environments. Each workspace has its own settings and no data crosses workspace boundaries.
How do I use workspaces for client separation?
Create a workspace for each client. Build their apps, connect their integrations, and invite their team members to that specific workspace. Each client sees only their own data and apps. You maintain admin access across all workspaces to manage the relationships.
Can team members belong to multiple workspaces?
Yes. Users can be invited to multiple workspaces with different permission levels in each. You might be an admin in your primary workspace, an editor in a client workspace, and a viewer in a partner workspace. Switch between workspaces from the dashboard.
How do workspaces relate to data isolation?
Within a workspace, all apps share access to the entity graph—your Customer entity is available to every app in that workspace. Across workspaces, data is completely isolated. Even if you have admin access to multiple workspaces, the data never mixes.

Related Features

See How Teams Use Workspaces

Ready to try Workspaces?

Start vibe-coding with Runwork today.