# Setup

{/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/db-leads/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */}

<Lead>
Freshly installed, DB-Leads is empty, and an empty tool does not say what to do next. So on first open you land in **setup**: a page of its own, without the toolbar and without empty tabs, that leads to the first result in five steps. Each step has its own page, with next and back.
</Lead>

## The five steps

<Steps>
  <Step title="Choose a data source">
    Two paths. **Connect my onOffice** is the right one if you intend to use the tool: enter credentials, verify the connection. **Look around with samples first** loads a small, clearly labelled demo book you can use to try every feature without touching real data.
  </Step>
  <Step title="Import your book">
    The first sync pulls addresses and activities from onOffice. It runs in the background and is resumable; you can leave the page and move on to the next step while it runs. With several thousand addresses the first run takes accordingly long. Every later run only fetches what changed since the last one and finishes in seconds.
  </Step>
  <Step title="Connect results back to onOffice">
    Defines which onOffice fields the assessment is written into (persona, signals, sales readiness, summary). The field guide on this page tells you which fields to create in onOffice and checks afterwards whether they are in place. Optional, but the step that turns an assessment inside our tool into an entry in your CRM. See [onOffice import](/tools/db-leads/onoffice-import).
  </Step>
  <Step title="Opt-outs">
    Anyone who has already said no must never be suggested or contacted. Here you import an opt-out list from a previous system or map the onOffice flag that carries the objection. The step is optional: an office without an old list simply continues, and objections that later arrive through an unsubscribe link apply immediately anyway. It sits deliberately before the first scan, because importing it afterwards would be one round too late.
  </Step>
  <Step title="Start the first scan">
    The [database scan](/tools/db-leads/datenbank-scan) works through the imported book and puts the first findings into the inbox. At the end, setup shows an overview of what is in place and takes you to the findings.
  </Step>
</Steps>

## Every step has an address

Setup lives at `/tools/db-leads/setup`, each step below it (for example `/tools/db-leads/setup/fields`). A link to a step lands exactly there, the browser's back button goes one step back, and a reload keeps you where you were. Without a step in the address, the first open step opens.

## Stopping is expected

No step has to be finished in one sitting. Setup re-reads what is already done every time it opens, and the **list icon in the toolbar** brings you back at any time, even long after setup is complete. That is the way to catch up on the field mapping later.

## Sample data

The sample data is labelled as such everywhere and **disappears automatically** as soon as you connect your real onOffice. It is meant for looking, not for working: no real tasks are created from it and no mail goes out.

<Warning title="What setup cannot do">
It does not create onOffice fields. If your CRM lacks the target fields for the assessment, you have to create them there once. The field guide in the third step tells you which ones and checks afterwards whether it worked. The instructions are also under [onOffice import](/tools/db-leads/onoffice-import).
</Warning>

## What to do next

<CardGrid>
  <Card title="Configure qualification" href="/tools/db-leads/einstellungen">Tailor personas, signals and sales readiness to your office.</Card>
  <Card title="Release your own fields" href="/tools/db-leads/onoffice-import">The CRM fields the analysis may additionally read.</Card>
  <Card title="Permissions" href="/tools/db-leads/berechtigungen">Who on the team may do what.</Card>
</CardGrid>