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

# Getting Started

> Set up a client's work once, and Flows makes the dated jobs, tracks the time, and turns it all into invoices.

Denari Flows runs your firm's recurring work end to end: the agreement with a client, the dated jobs that come out of it, the tasks people work, the time they log, and the invoices that follow.

<Note>
  Your firm needs to have the Denari Flows component enabled in order to use it.
  If you can't see Flows in the product switcher and have questions, please
  contact the Denari or IT admin at your firm.
</Note>

## The one idea

**An engagement is the standing agreement with a client, and almost everything else is made from it.** You describe a client's work once: which of their entities you serve, which services you provide, how each one is scheduled, and how it is priced. You turn the engagement on. From then on, Flows makes the dated jobs, fills them with tasks, tracks the time people spend, and gathers the finished work into bills.

## The life of the work

<Steps>
  <Step title="Set up the client">
    Add the client and its entities, and say who the partner and managers are.
    See [Clients & entities](/flows/clients-and-entities).
  </Step>

  <Step title="Set up the engagement">
    Pick the entities, add the services, and choose how each one is billed. See
    [Engagements](/flows/engagements).
  </Step>

  <Step title="Turn it on">
    An admin clicks **Activate**. Nothing happens until this step.
  </Step>

  <Step title="Flows makes the projects">
    Each service makes one dated project per period, such as *Monthly
    bookkeeping, Sep 2026* or *1120S, FY2025*. See [Projects](/flows/projects).
  </Step>

  <Step title="People do the tasks">
    Each project comes with its tasks, in order, with due dates and owners.
    People log time as they work. See [My Work](/flows/my-work) and
    [Time](/flows/time).
  </Step>

  <Step title="Billing turns work into invoices">
    Each billing group gets one invoice per billing period. You review the
    draft, issue it, send it, and record the payment. See
    [Billing](/flows/billing).
  </Step>
</Steps>

## Rules worth knowing up front

* **Nothing runs until the engagement is active.** No projects, no tasks, no bills.
* **The engagement is the plan. Projects are copies of it at a point in time.** Changing a service later changes future projects. It does not quietly rewrite projects that already exist.
* **Adding a service later is not a special case.** It is just another service on the engagement, and it starts making its own projects on its own schedule.
* **One invoice per billing group per billing period.** Everything that group owes for that stretch of time lands on one invoice, split into sections.
* **Issued invoices never change.** To fix one, you use a credit note or a void. Nothing about money is deleted; corrections are added as new entries you can see.

## Getting around

Select **Flows** from the product switcher in the top left. The sidebar has four sections.

<img src="https://mintcdn.com/denari/BjswZVn-VPq93yoD/images/flows/flows-sidebar.png?fit=max&auto=format&n=BjswZVn-VPq93yoD&q=85&s=dbdd6f3cca16a62f2252b850ea368ec7" alt="The Flows sidebar beside the Clients list, with General, Clients, Sales, and Configure sections." style={{ borderRadius: "0.5rem" }} width="1600" height="1000" data-path="images/flows/flows-sidebar.png" />

| Section | Pages | What they are for |
| - | - | - |
| **General** | Overview, My Work, Available work, Projects, Time | Your daily work, starting with Overview. |
| **Clients** | Clients, Engagements, Billing groups, Invoices, Payments, Agreements | Setting up clients and their work, and billing them. |
| **Sales** | Pipeline, Referral Sources | Tracking prospects before they become clients. |
| **Configure** | Service templates, Bill rates, Tags | Firm-wide setup. Only admins see this section. |

When a timer is running, a small clock next to your avatar at the top of the page shows its time, on every page. Click it to stop the timer. See [Time](/flows/time#the-timer).

## Overview

**Overview** is your daily briefing.

* **Mine** is your own work. **Projects** lists the projects you're on, with buttons for **Ready**, **Overdue**, **Due this week**, and **Over budget**; each row shows the next step and when it's due. **Time** shows your hours this week against your weekly target, how much is billable, and any days with no time logged.
* **My clients** covers the clients where you hold the Partner seat, or the Manager seat for a service. Admins see **All clients** instead. Narrow it with **All services** and **All teams**. Its **Projects** adds **Waiting** (someone owns the next step), **Unassigned** (nobody does), and **Bill review** (an invoice waiting on someone's review). **Time** shows each person's hours and missing days, and **People** shows each person's waiting, overdue, due-this-week, and over-budget projects.

<Note>
  Counts are projects, not tasks. **Due this week** means the next 7 days.
</Note>

## Who can do what

Some actions are for **firm admins** only:

* Creating, activating, deactivating, and archiving engagements
* Generating projects by hand
* Editing service templates, bill rates, and tags
* Every billing action: making drafts, issuing invoices, recording payments, and changing billing settings

Everyone else can open most pages and see the information. They just don't see the buttons for those actions. The exception is **Bill rates**, which only admins can open.

## Where to start, by role

| You are | Read |
| - | - |
| **An admin setting up the firm** | [Clients & entities](/flows/clients-and-entities), [Periods](/flows/periods), [Service templates](/flows/service-templates), [Engagements](/flows/engagements), [Pipeline](/flows/pipeline) |
| **A preparer or reviewer** | [Projects](/flows/projects), [My Work](/flows/my-work), [Task rules](/flows/task-rules), [Time](/flows/time) |
| **A partner or manager** | [Clients & entities](/flows/clients-and-entities), [Engagements](/flows/engagements), [Projects](/flows/projects), [My Work](/flows/my-work) |
| **A biller** | [Billing](/flows/billing), then the billing pages in order |

<CardGroup cols={2}>
  <Card title="Clients & entities" icon="users" href="/flows/clients-and-entities">
    Who you work for, and who plays which part.
  </Card>

  <Card title="Engagements" icon="file-signature" href="/flows/engagements">
    The standing agreement everything is made from.
  </Card>

  <Card title="Projects" icon="folder" href="/flows/projects">
    The dated jobs, and how due dates work.
  </Card>

  <Card title="My Work" icon="list-checks" href="/flows/my-work">
    Find, claim, and work your tasks.
  </Card>

  <Card title="Time" icon="clock" href="/flows/time">
    Log time, run a timer, and read the timesheet.
  </Card>

  <Card title="Billing" icon="receipt" href="/flows/billing">
    From work done to invoice paid.
  </Card>

  <Card title="Glossary" icon="book-open" href="/flows/glossary">
    Every word you'll see, in plain terms.
  </Card>

  <Card title="That looks wrong" icon="circle-help" href="/flows/faq">
    The likely reason, by topic.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.