Moving to another step replaces whatever is in the input with that step's prompt. Send — or copy out — what you are part-way through typing before you press **‹** or **›**.
## Starting a Workflow
There are two ways in.
**From the Templates library.** Click **Templates** in the global part of the sidebar, open the **Workflows** tab, and click **Run** on the Workflow's card. A new chat opens with the Workflow loaded at step 1 and that step's prompt already in the input, ready for you to edit and send.
**From a chat.** In the composer, choose **Tools → Workflows**. The picker lists what you can run under **All**, **Yours**, **Shared** and **Libra**, with the usual jurisdiction, practice-area and tag filters. Picking one loads it into the chat you are already in and switches the chat to the Assistant on step 1. In a chat that already has messages, the Workflow attaches without touching the input — nothing you have typed is overwritten until you move between steps.
## Working through the steps
Once a Workflow is active, a compact row appears **inside the composer, just above where you type** — not at the top of the chat. Reading left to right it shows the Workflow icon, the step Assistants stacked as overlapping avatars, the Workflow's name, a chevron, and then the Assistant handling the step you are on. Directly after that comes the step counter — rendered as **2 / 4** — between **‹** and **›** buttons. At the far right of the row sits an **✕** that removes the Workflow.
Nothing advances on its own. When a step's answer comes back, Libra stays where it is; you decide the step is finished and move on.
* **‹** and **›** step back and forward one at a time, and stop at the first and last step.
* Hover the current Assistant's name and a **Steps** list opens showing every step in order. Click any entry to jump straight there — useful for skipping ahead or going back several steps at once.
* Hover the Workflow's name instead and you get the whole numbered step list as a tooltip, without leaving the step you're on.
* However you move, Libra switches the chat to that step's Assistant and puts that step's prompt into the input. Edit it before you send, or send it as written.
* Up to three of the current Assistant's suggested prompts appear as buttons in a row underneath. Clicking one writes it into the input; you still choose when to send.
* **✕** takes the Workflow off the chat and returns it to an ordinary chat. The messages you have already exchanged stay where they are.
## What a Workflow is made of
| Component | What it is |
| ------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Steps** | Each step is one Assistant, picked for that stage of the job. |
| **Order** | The order you set in the editor is the order the pager walks through. |
| **Per-step prompt** | An optional pre-written message stored with the step. Libra drops it into the input when you arrive at that step. |
Suggested prompts come from the Assistant on the step, not from the Workflow — tune them on the Assistant and every Workflow that uses it picks them up.
## When to use Workflows
| Use case | Example |
| ---------------------------------- | ------------------------------------------------------------------------------------ |
| **Multi-step analysis** | *Extract facts → Identify legal issues → Research relevant case law → Draft a brief* |
| **Consistent firm-wide processes** | *Client intake form → Conflict check → Engagement letter draft* |
| **Quality control** | *First draft → Self-review with checklist → Final formatting* |
| **Team standardisation** | Every associate runs the same NDA-drafting Workflow, so the output is consistent. |
A Workflow needs at least two Assistants before it can be saved or run. For a task that only needs one, use that Assistant on its own — Workflows pay off when there are at least two distinct stages.
## Where Workflows live
Workflows are templates. They live in the global [Templates library](/en/features/templates/about) under the **Workflows** tab, alongside the **Assistants**, **Reviews** and **Discoveries** tabs, and any project can run them.
## Common Workflow examples