> ## Documentation Index
> Fetch the complete documentation index at: https://floutwork.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces: separate contexts for every project

> Keep clients, projects, and roles neatly separated in Floutwork. Each workspace holds its own apps and tabs so work never bleeds together.

Workspaces are Floutwork's answer to context-switching. Instead of juggling tabs across a single cluttered browser, you create a dedicated workspace for each project, client, or role — then switch between them with one click. Every workspace remembers its own open apps and tabs exactly as you left them.

## What is a workspace?

A **Workspace** is a self-contained environment inside Floutwork. Each one holds its own set of open web apps and tabs, grouped by app. When you switch workspaces, Floutwork instantly restores the apps and tabs for that context, so you never have to hunt for where you were.

Think of each workspace as a separate desk — one for your client work, one for your side project, one for internal tools — all inside a single window.

## How to create a workspace

<Steps>
  <Step title="Open the Workspaces panel">
    Click the **Workspaces** icon in the left sidebar to open the workspace switcher.
  </Step>

  <Step title="Add a new workspace">
    Click **+ New Workspace** at the bottom of the panel. Give it a clear name — for example, "Client A", "Marketing", or "Side Project".
  </Step>

  <Step title="Set up your apps">
    Open the web apps you need for that workspace from the **Launchpad**. Floutwork groups each app's tabs together automatically.
  </Step>

  <Step title="Start working">
    Everything you open stays in this workspace until you close it. Next time you switch back, your apps reopen exactly where you left off.
  </Step>
</Steps>

## Switching between workspaces

Click any workspace name in the left sidebar to switch to it instantly. Floutwork saves the state of your current workspace — open tabs, scroll position, and all — and restores the one you're switching to.

<Tip>
  Assign distinct names to each workspace so the switcher stays scannable at a glance. Short names like "Client A", "Design", or "Admin" work better than long descriptive phrases.
</Tip>

## The Shared Workspace

Floutwork includes a built-in **Shared Workspace** that sits alongside your personal workspaces. Use it for tools you rely on across every context — your calendar, a company wiki, or an internal dashboard. Apps in the **Shared Workspace** are always accessible regardless of which workspace you're currently in.

## Use cases

<CardGroup cols={2}>
  <Card title="Client work" icon="briefcase">
    Give each client their own workspace. Gmail threads, project docs, and task boards for one client stay completely separate from another's.
  </Card>

  <Card title="Different roles" icon="user">
    Switch between a "PM" workspace (Jira, Linear, Notion) and a "Design" workspace (Figma, Zeplin, Dribbble) without mixing tabs.
  </Card>

  <Card title="Side projects" icon="flask">
    Keep your side project's research, notes, and tools isolated from your day job so you can context-switch cleanly.
  </Card>

  <Card title="Environments" icon="server">
    Maintain separate workspaces for staging and production dashboards to avoid acting on the wrong environment by mistake.
  </Card>
</CardGroup>

## Keeping workspaces focused

<Tip>
  Resist the urge to open every tool in every workspace. Pin only the apps that are directly relevant to that workspace in the **Launchpad** — a leaner workspace is faster to navigate and easier to return to after a break.
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Launchpad" icon="rocket" href="/workspace/launchpad">
    Pin your most-used web apps so you can launch them into any workspace in one click.
  </Card>

  <Card title="Smart browser" icon="globe" href="/features/smart-browser">
    Learn how Floutwork's built-in work browser keeps tabs grouped by app within each workspace.
  </Card>
</CardGroup>