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

# Fintheon Desk 2.0

> The next Fintheon workspace: a permissioned environment for market investigation, collaboration, and durable analysis.

Desk 2.0 is the next workspace inside Fintheon. It gives a trader one place to investigate a market target, build an analysis session, work with collaborators and agents, and return to that work later with its evidence intact.

The current Fintheon Home experience remains the market cockpit. Desk is a separate workspace for the deeper work that follows: research, structured analysis, shared artifacts, and collaboration.

<Note>
  Desk 2.0 is the documented product direction. The foundational shell exists, while the connected end-to-end workflow is still being built and verified.
</Note>

## The operating model

A Desk session follows one continuous path:

1. Find a market target.
2. Start a governed analysis session.
3. Create or attach a working artifact.
4. Open the context that supports the decision.
5. Save the session and restore it later.
6. Return to the same Desk state without losing the thread.

This keeps a market investigation from becoming a collection of disconnected chats, charts, and notes.

## The workspace

Desk uses one stable left sidebar, one central work surface, and an on-demand details drawer.

* The **left sidebar** holds the Desk Suite pages, history, search, and navigation.
* The **center** changes to fit the work: a room, analysis stage, narrative surface, presentation, or artifact.
* The **Strategium drawer** opens only when needed for threads, files, artifacts, and participants.

## What Desk connects

Desk 2.0 connects the existing Fintheon strengths without moving the Home cockpit or rewriting its protected chart and terminal surfaces:

* market context through the versioned Fintheon data adapters;
* research and reasoning through governed agent sessions;
* collaboration through rooms, direct messages, artifacts, threads, and presence;
* narrative and annotation through NarrativeFlow, DeskMap, charts, and QuantComposer;
* durable return paths through history, saved context, and parent-linked artifacts.

## Read next

<CardGroup cols={2}>
  <Card title="Desk Suite" icon="table-columns" href="/desk-2/suite">
    Learn what each Desk page is for.
  </Card>

  <Card title="Collaboration and context" icon="people-group" href="/desk-2/collaboration">
    See how rooms, agents, and private context work together.
  </Card>

  <Card title="Delivery status" icon="road" href="/desk-2/delivery-status">
    Separate the planned product from the work that is already complete.
  </Card>
</CardGroup>